From: Eric S Fraga <esflists@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: cautionary tale: avoid creating/using a macro called "title"
Date: Thu, 22 Mar 2018 12:12:58 +0000 [thread overview]
Message-ID: <87370s8g1h.fsf@gmail.com> (raw)
In-Reply-To: <87d0zwv41o.fsf@gnu.org> (Bastien's message of "Thu, 22 Mar 2018 10:43:31 +0100")
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On Thursday, 22 Mar 2018 at 10:43, Bastien wrote:
> I hate to suggest this, but could there be something wrong in your
> installation?
Hi Bastien,
don't hesitate at all to suggest this! There's always that
possibility. :-( I don't think I have a mixed installation although I'm
not sure how to verify this.
Now, the really interesting thing is that if I use emacs -Q and try
exporting the file with the version of org that comes with the latest
emacs snapshot,
GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.29) of 2018-03-18, unofficial emacs-snapshot build: http://emacs.secretsauce.net
Org mode version 9.1.6 (release_9.1.6-50-g96b33f @ /usr/share/emacs/27.0.50/lisp/org/)
the export works!
If I emacs -Q and make sure the load path points to the git version of
org, it doesn't work. When I do so, I have
Org mode version 9.1.6 (release_9.1.6-341-g3a4fd3 @ /home/ucecesf/git/org-mode/lisp/)
and git status says:
--8<---------------cut here---------------start------------->8---
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
--8<---------------cut here---------------end--------------->8---
I do not understand why the org version is not 9.1.8. What does your
say?
>> In any case, no worries as simply changing the macro name (& subsequent
>> use) to titlecontents or similar does the job.
>
> Well, even if the workaround works, I think we should prevent Org from
> crashing here.
Indeed, but I am stuck as to how to proceed. Suggestions welcome, of
course!
Thanks,
eric
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-341-g3a4fd3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2018-03-22 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 17:37 cautionary tale: avoid creating/using a macro called "title" Eric S Fraga
2018-03-21 1:06 ` Bastien
2018-03-21 11:01 ` Eric S Fraga
2018-03-22 8:34 ` Bastien
2018-03-22 8:55 ` Eric S Fraga
2018-03-22 9:22 ` Eric S Fraga
2018-03-22 9:43 ` Bastien
2018-03-22 12:12 ` Eric S Fraga [this message]
2018-03-22 12:23 ` Kaushal Modi
2018-03-22 15:34 ` Eric S Fraga
2018-03-22 13:28 ` Nicolas Goaziou
2018-03-22 16:39 ` Eric S Fraga
2018-03-23 22:42 ` Nicolas Goaziou
2018-03-24 17:54 ` Eric S Fraga
2018-04-26 23:34 ` Bastien
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=87370s8g1h.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).