Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved support for space-containing file paths #514

Merged
merged 8 commits into from
Feb 11, 2025

Conversation

rjkroege
Copy link
Owner

  • Add a better E
  • remove unnecessary named return value
  • Remove superfluous assignments
  • Refactoring for better file-with-spaces handling
  • Robustness improvement in file name expansion
  • Added some code to provide better debugging support.
  • Fix bug in opening file whose names contains spaces
  • Support setting names from the filesystem that have spaces

@rjkroege rjkroege force-pushed the E_with_spaces_upstream branch from c17f678 to a346989 Compare February 11, 2025 05:52
Plan9 port comes with a command E. E is a shell script that opens a
file for editing and blocks until one closes it in Acme/Edwood. P9P E
does not work for files whose names contain spaces. So this CL adds a
new E implementation in Go that should support file names containing
spaces. It doesn't yet do so because of bugs in Edwood.

Also updated go.mod for E commandt ake sure that the go.mod and go.sum
are correct for the deps needed.

Also updated the code for the new version of staticcheck.
Partial work to improve how Edwood handles files whose names contain
spaces.
The code to open files whose names contain spaces had an off-by-1
error and didn't work when right-clicking a selection including
quotes. Fix this.
With this change, the E command landed earlier will work for files
whose names contain spaces as the change permits setting file paths to
contain spaces.
@rjkroege rjkroege force-pushed the E_with_spaces_upstream branch from a346989 to 384fce8 Compare February 11, 2025 07:07
@rjkroege rjkroege merged commit e324f39 into master Feb 11, 2025
6 checks passed
@camsn0w
Copy link
Contributor

camsn0w commented Feb 12, 2025

🎊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants