From: Eric Fraga <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com, Nicolas Goaziou <firstname.lastname@example.org> Subject: Re: orgstuct++ does not lurk silently in the shadow Date: Sun, 6 May 2012 23:39:38 +0930 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Bastien's message of "Sun, 6 May 2012 10:07:43 +0200") Bastien <email@example.com> writes: > Hi Nicolas, > > Nicolas Goaziou <firstname.lastname@example.org> writes: > >> ((adaptive-fill-function (quote nil)) (adaptive-fill-regexp (quote \(\([ > > [...] > > This looks good. > >> It's the same as the previous bug: when I try to debug >> `org-indent-line-function', the problem disappears. > > I pushed another fix: I now rely on the existing org-let > function, which safely evaluate let constructs. Bastien, unfortunately, I still have problems. I am using org completely up to date (a few minutes ago). I do not turn orgstruct++-mode on automatically at all any more but instead turn it on manually by M-x orgstruct++-mode RET once I'm in a Message buffer. I tried it just now, replying to your email as my test. Turned on the mode, tried to fill the quoted text and it all got mixed up. Undid that. Then went to the bottom and tried to insert a new line and got: org-indent-line-function: Lisp nesting exceeds `max-lisp-eval-depth' Turned off orgstruct++-mode (by M-x ... RET again) and filling of quoted text works fine as does normal writing. I will try (tomorrow) to isolate this with emacs -Q but my problem is that my gnus configuration is really really messy and difficult to isolate. Thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 18.104.22.168 : using Org release_7.8.09-489-g541288
next prev parent reply other threads:[~2012-05-06 14:09 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-08 7:08 Christopher Schmidt 2012-03-08 13:38 ` orgstruct++ does not lurk silently in the shadow (was: orgstuct++ does not lurk silently in the shadow) Christopher Schmidt 2012-04-25 7:44 ` orgstuct++ does not lurk silently in the shadow Eric Fraga 2012-04-26 10:42 ` Bastien 2012-04-29 6:40 ` Eric Fraga 2012-04-29 6:48 ` Eric Fraga 2012-04-29 8:38 ` Bastien 2012-04-29 11:05 ` Christopher Schmidt 2012-04-29 12:27 ` Christopher Schmidt 2012-05-01 17:43 ` Bastien 2012-05-03 9:56 ` Eric Fraga 2012-05-03 12:28 ` Bastien 2012-05-03 12:58 ` Nicolas Goaziou 2012-05-03 13:12 ` Bastien 2012-05-03 13:17 ` Nicolas Goaziou 2012-05-03 13:45 ` Bastien 2012-05-03 15:53 ` Nicolas Goaziou 2012-05-05 13:46 ` Bastien 2012-05-05 15:51 ` Nicolas Goaziou 2012-05-05 16:18 ` Bastien 2012-05-05 16:19 ` Nicolas Goaziou 2012-05-05 16:22 ` Bastien 2012-05-05 16:30 ` Nicolas Goaziou 2012-05-06 8:07 ` Bastien 2012-05-06 14:09 ` Eric Fraga [this message] 2012-05-06 14:27 ` Thorsten Jolitz 2012-05-06 15:47 ` Bastien 2012-05-07 4:23 ` Eric S Fraga 2012-05-08 12:31 ` Bastien 2012-05-08 23:54 ` Eric S Fraga
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: orgstuct++ does not lurk silently in the shadow' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).