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.

Sign up for GitHub

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

Jump to bottom

multi-libvterm function no longer accepts buffer name argument #6

Open
paulbdavis opened this issue Mar 28, 2020 · 0 comments · May be fixed by #7
Open

multi-libvterm function no longer accepts buffer name argument #6

paulbdavis opened this issue Mar 28, 2020 · 0 comments · May be fixed by #7

Comments

@paulbdavis
Copy link

paulbdavis commented Mar 28, 2020 •
edited
Loading

Since the last update was merged, I am no longer able to provide a buffer name to the multi-libvterm function. Looks like the argument was removed?

EDIT: Not really sure how this actually works, but just adding the optional argument back in and nothing else results in the previous behaviour.. I'm sure it's something I just don't understand about elisp (is the optional arg being passed through implicitly somhow??)

Sending a PR that reverts the behavior for review
@paulbdavis paulbdavis linked a pull request Mar 28, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

re-add optional argument paulbdavis/multi-libvterm
1 participant
@paulbdavis