emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: cautionary tale: avoid creating/using a macro called "title"
Date: Thu, 22 Mar 2018 12:23:00 +0000	[thread overview]
Message-ID: <CAFyQvY27S4RCHmmo2jT8QSp5HaCdUvLdego6BYvY5DHYUbOK6A@mail.gmail.com> (raw)
In-Reply-To: <87370s8g1h.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

On Thu, Mar 22, 2018, 8:14 AM Eric S Fraga <esflists@gmail.com> wrote:

>
> 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/)
>

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.

I had written a post to fix such issues and be able to specifically use Org
(1) that ships with Emacs (2) from Elpa, or (3) from git.

Sorry if you have already read it and this sounds like spam:
https://scripter.co/building-org-development-version/.

> --

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1395 bytes --]

  reply	other threads:[~2018-03-22 12:23 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 [this message]
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=CAFyQvY27S4RCHmmo2jT8QSp5HaCdUvLdego6BYvY5DHYUbOK6A@mail.gmail.com \
    --to=kaushal.modi@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).