From: Eric S Fraga <esflists@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: cautionary tale: avoid creating/using a macro called "title"
Date: Thu, 22 Mar 2018 15:34:38 +0000 [thread overview]
Message-ID: <87r2oc5dkh.fsf@ucl.ac.uk> (raw)
In-Reply-To: CAFyQvY27S4RCHmmo2jT8QSp5HaCdUvLdego6BYvY5DHYUbOK6A@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Thursday, 22 Mar 2018 at 12:23, Kaushal Modi wrote:
>
> Org is probably getting loaded before you tweak the load paths. e.g. emacs
> -Q foo.org would do that. That version looks like the one that's on
> emacs-26/master branch of Emacs.
Thank you. What is the number after the 9.1.6- in the org version for
yours? I do not load the file immediately. My means of testing is:
emacs -Q
evaluate
#+begin_src emacs-lisp
(add-to-list 'load-path "~/git/org-mode/lisp")
(require 'org)
#+end_src
and then visit foo.org to test.
I get a different version of org (differing in the number of 9.1.6-) if
I evaluate that lisp code when compared to not evaluating it.
Thanks again,
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 15:34 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
2018-03-22 12:23 ` Kaushal Modi
2018-03-22 15:34 ` Eric S Fraga [this message]
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=87r2oc5dkh.fsf@ucl.ac.uk \
--to=esflists@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).