From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]
Date: Sat, 03 Jun 2017 22:46:01 +0200 [thread overview]
Message-ID: <87a85olrzq.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20170603114859.GE7145@seven> (Stefan-W. Hahn's message of "Sat, 3 Jun 2017 13:48:59 +0200")
Hello,
"Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
> I use a minor mode (moccur-edit-mode, seems a little bit old) which
> initializes one variable in this way:
>
> ,----
> | (defvar moccur-edit-old-content)
> | (make-local-variable 'moccur-edit-old-content)
> `----
>
> This leads to following result in (buffer-local-variables):
>
> ,----
> | ... (moccur-edit-file-overlays) moccur-edit-old-content (company-prefix) ...
> `----
>
> I think this is correct and happens not only by the used minor-mode.
>
> When doing org-capture now I got a lisp error:
>
> Debugger entered--Lisp error: listp moccur-edit-old-content
>
> This error comes from org-clone-local-variables, because there the
> prediction for local variables is always to be a list.
Fixed. Thank you for the report and the analysis.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-06-03 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 11:48 Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)] Stefan-W. Hahn
2017-06-03 20:46 ` Nicolas Goaziou [this message]
2017-06-04 6:57 ` Stefan-W. Hahn
2017-06-04 7:19 ` Nicolas Goaziou
2017-06-04 8:08 ` Stefan-W. Hahn
2017-06-04 8:24 ` Nicolas Goaziou
2017-06-04 9:18 ` Stefan-W. Hahn
2017-06-04 9:35 ` Nicolas Goaziou
2017-06-04 9:52 ` Stefan-W. Hahn
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 \
--in-reply-to=87a85olrzq.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=stefan.hahn@s-hahn.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).