-
Notifications
You must be signed in to change notification settings - Fork 2
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 buffer switching (issue #25) #26
Conversation
Co-authored-by: japanoise <japanoise@users.noreply.github.com>
Need to redesign this.
I will resolve the conflicts now and resubmit. i put it in draft meanwhile. |
OK fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some changes to make here but broadly this looks good.
Co-authored-by: japanoise <japanoise@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I implemented Stretchy buffer in tabCompleteFilenames for more efficient handling of lots of buffers. I did notice along the way that editorKillLine which I introduced doesn't put the killed text on the kill ring, however neither does editorKillLineBackwards. I opened issue #27 for that.
g2g |
next buffer C-x right
previous buffer C-x left
and C-x b (which used to be next buffer) now lets you cycle through buffer names. The buffer name completion is based on how filename completion works in FInd FIle
changed from [ to * for special buffers eg scratch instead of [scratch]. This is because when people switch buffers they are used to typing C-x b *sc RET to go to scratch
REF: issue #25