issue/white-spaces-and-returns #12
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
vulpinelinux/cvsh!12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "charlie/cvsh:issue/white-spaces-and-returns"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Syncing so it matches the available
vpmpackage but I addedreturnbuiltin that exits the current command handler and moves the config loading so it only happens for interactive sessions. This resolved a bug where usingscpwould conflict due to it always assuming a session is interactive; it isn't.Added
cvsh --versionexit before touching the config and delegated all command-line invocations with arguments (except -v/--version) to /bin/sh so we can do things likecvsh -c 'echo hello'which solves another remote ssh issue - as previously it always assumed interactive for that too and wouldn't pass along-ccommand evocations when sending a command over ssh rather than doing an interactive session. I also moved all non-interactive stdin (e.g. pipes and redirected input) to /bin/sh to be written properly under the new style guide and intent-fully as the previous kept causing issues with non-interactive shells.This resolved a number of bugs by treating
/bin/shwhich is inherent in busy-box as the fallback while we revise cvsh to handle non-interactive sessions properly.Assigned to @verysmallrat as I know they'll be doing a
3.5.11taking over from this point now it's inline with the coding style-guide and setup for further development under the proposed plans while handling both interactive and non-interactive shells gracefully.read but untested by me.