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

indent-guide breaks in c/c++ mode #40

Open
matth3wkim opened this issue Apr 14, 2016 · 2 comments
Open

indent-guide breaks in c/c++ mode #40

matth3wkim opened this issue Apr 14, 2016 · 2 comments
Assignees
Labels

Comments

@matth3wkim
Copy link

はじめまして。 僕は韓国でEmacsをつかってるひとです。 日本語が下手ですみません。
僕はzk-phiさんのindent-guideのbig fanです。それは僕のfavoriteなmode中一つです。
最近c言語で仕事していますが、小さな問題を見つけました。
c-modeでindent-guideは結構よく作動しますが、時々error-messageを出しながら
breakになります。 僕の日本語で説明ができるかどうか確信がないので
僕のつかってるinit.el fileとerror videoのlinkを残ります。
御覧下さってもらいたいんです。

http://firetux.blog.me/220683656291

@zk-phi
Copy link
Owner

zk-phi commented Apr 17, 2016

"kamsahamnida" for your japanese report!

hmm.., I couldn't reproduce the error on my machine.
私の環境ではエラーが再現しませんでした。

can you show me the backtrace ? (enable debug-on-error with M-x toggle-debug-on-error then reproduce the error)
backtrace を見せていただけますか? (M-x toggle-debug-on-error で debug-on-error を有効にして、エラーを再現してください)

@matth3wkim
Copy link
Author

どうもありがとうございます。 はい。 これはBacktraceの結果です。

Debugger entered--Lisp error: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
#[(ov) "\301�\302"\303=\205\n��\207" [ov overlay-get category indent-guide] 3](#<overlay from 854 to 854 in ls.c)
mapcar(#[(ov) "\301�\302"\303=\205\n��\207" [ov overlay-get category indent-guide] 3](#<overlay from 854 to 854 in ls.c> #<overlay from 852 to 852 in ls.c> #<overlay from 840 to 840 in ls.c> #<overlay from 839 to 839 in ls.c> #<overlay from 837 to 837 in ls.c> #<overlay from 820 to 820 in ls.c> #<overlay from 792 to 792 in ls.c> #<overlay from 791 to 791 in ls.c> #<overlay from 766 to 766 in ls.c> #<overlay from 753 to 753 in ls.c> #<overlay from 752 to 752 in ls.c> #<overlay from 750 to 750 in ls.c> #<overlay from 732 to 732 in ls.c> #<overlay from 728 to 728 in ls.c> #<overlay from 722 to 722 in ls.c> #<overlay from 721 to 721 in ls.c> #<overlay from 713 to 713 in ls.c> #<overlay from 681 to 681 in ls.c> #<overlay from 641 to 641 in ls.c> #<overlay from 604 to 604 in ls.c> #<overlay from 603 to 603 in ls.c> #<overlay from 595 to 595 in ls.c> #<overlay from 572 to 572 in ls.c> #<overlay from 538 to 538 in ls.c> #<overlay from 507 to 507 in ls.c> #<overlay from 468 to 468 in ls.c> #<overlay from 467 to 467 in ls.c> #<overlay from 382 to 382 in ls.c> #<overlay from 381 to 381 in ls.c> #<overlay from 377 to 377 in ls.c> #<overlay from 342 to 342 in ls.c> #<overlay from 341 to 341 in ls.c> #<overlay from 303 to 303 in ls.c> #<overlay from 302 to 302 in ls.c> #<overlay from 290 to 290 in ls.c> #<overlay from 246 to 246 in ls.c> #<overlay from 245 to 245 in ls.c> #<overlay from 220 to 220 in ls.c> #<overlay from 207 to 207 in ls.c> #<overlay from 206 to 206 in ls.c> #<overlay from 179 to 179 in ls.c> #<overlay from 154 to 154 in ls.c> #<overlay from 153 to 153 in ls.c> #<overlay from 127 to 127 in ls.c> #<overlay from 126 to 126 in ls.c> #<overlay from 104 to 104 in ls.c> #<overlay from 103 to 103 in ls.c> #<overlay from 84 to 84 in ls.c> #<overlay from 64 to 64 in ls.c> #<overlay from 44 to 44 in ls.c> ...))
indent-guide--active-overlays()
indent-guide-show()
indent-guide-show()
.
.
.
indent-guide-show()
indent-guide-show()
indent-guide-show()
indent-guide-show()
#nil "\301 \210\302\211�\207" [indent-guide--timer-object indent-guide-show nil] 2
apply(#[nil "\301 \210\302\211�\207" [indent-guide--timer-object indent-guide-show nil] 2] nil)
byte-code("r\301�\302H�\303H"\210)\301\207" [timer apply 5 6] 4)
timer-event-handler([t 0 0 100000 nil #[nil "\301 \210\302\211�\207" [indent-guide--timer-object indent-guide-show nil] 2] nil idle 0])

C-modeでのERRORは(setq indent-guide-recursive t)を使う時発生することを発見しました。
色々わざわざ気を使ってくださってありがとうございます。

結果全文:http://blog.naver.com/firetux/220686167218

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

No branches or pull requests

2 participants