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

Parser gremlins / issue tracker. #1

Open
geoff-nixon opened this issue Feb 7, 2014 · 0 comments
Open

Parser gremlins / issue tracker. #1

geoff-nixon opened this issue Feb 7, 2014 · 0 comments
Assignees
Milestone

Comments

@geoff-nixon
Copy link
Member

I frequently get what looks like the last couple of characters of an escape sequence showing up randomly with the modern parser that's enabled now by default. Unfortunately, I can't seem to reproduce it, regularly, but I've linked a log anyway; maybe it can still tell you something?

Also, please consider giving a second look to migrating the bug tracker to Github. I don't think the "attachments issue" is quite as much of an issue as one might think, if one were ask people submitting bugs to use the workflow I just did:

gem install gist (if you don't have it already)
screencapture -o itermscreenshot.png
gist -apc < /tmp/debuglog.txt (create anonymous private gist, put the link on my clipboard)
https://gist.github.com/anonymous/fc195009f2027c7ddedd (the log for this issue)
plutil -convert xml1 -o - ~/Library/Preferences/com.googlecode.iterm2.plist | gist -apc
https://gist.github.com/anonymous/291ea0f80bf480e9f602 (my preference file)
open https://github.com/gnachman/iTerm2/issues/new > Disabled, so forked here to illustrate.

Paste, type issue, drag in screenshot, done. Also, refer #2.
itermgremlins

@geoff-nixon geoff-nixon self-assigned this Feb 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant