emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Macro question with new texinfo exporter
Date: Sat, 16 Feb 2013 11:40:17 -0500	[thread overview]
Message-ID: <7168.1361032817@alphaville> (raw)
In-Reply-To: Message from Eric Abrahamsen <eric@ericabrahamsen.net> of "Sat, 16 Feb 2013 21:18:48 +0800." <87621s1jnr.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> wrote:

> Achim Gratz <Stromeko@nexgo.de> writes:
> 
> > Bastien writes:
> >> PS: I wonder if *any* of the menu item is used... as I don't use the
> >> menu myself, it's hard to tell.
> >
> > These days I only ever use it for "Show All" which does have a menu
> > entry, but no key binding.  But before I got used to where the keys are
> > I often used the menu to do things in tables, so I guess the menu gets
> > good use by other new users of Org (just that apparently none of them
> > tries to "reload Org uncompiled").
> 
> Related to this -- how do you folks handle multiple local git branches?
> Do you always run uncompiled, and follow every git checkout with
> org-reload? I've caught myself several times recently doing git
> checkouts and reloading, but of course still reloading the byte-compiled
> files from the previous branch....
> 

I don't trust org-reload enough for that: I write[fn:1] a minimal .emacs
that does whatever it needs to do to get me to the problem as fast as
possible and start a new emacs (emacs -q -l /path/to/minimal.emacs ...)

Nick

Footnotes:

[fn:1] "Write" is a bit of an exaggeration: I have a standard one that I copy and
       modify for my current needs. When I'm done, I throw it away.

  parent reply	other threads:[~2013-02-16 16:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 20:19 Macro question with new texinfo exporter Thomas S. Dye
2013-01-29 18:21 ` Nicolas Goaziou
2013-01-29 18:49   ` Thomas S. Dye
2013-01-30  9:22   ` Bastien
2013-01-30 12:44     ` Nicolas Goaziou
2013-01-30 16:14       ` Bastien
2013-01-30 22:24         ` Nicolas Goaziou
2013-01-31  2:21           ` Thomas S. Dye
2013-01-31 13:51           ` Bastien
2013-01-31 13:58             ` Nicolas Goaziou
2013-01-31 21:23             ` Nicolas Goaziou
2013-02-04 15:43               ` Thomas S. Dye
2013-02-04 17:26                 ` Bastien
2013-02-04 18:57                   ` Achim Gratz
2013-02-16  9:21                     ` Bastien
2013-02-16 10:19                       ` Achim Gratz
2013-02-16 10:34                         ` Bastien
2013-02-16 10:39                           ` Achim Gratz
2013-02-16 13:18                             ` Eric Abrahamsen
2013-02-16 13:23                               ` Reloading uncompiled and testing from several git branches (was: Macro question with new texinfo exporter) Bastien
2013-02-16 14:10                                 ` Reloading uncompiled and testing from several git branches Achim Gratz
2013-02-16 14:21                                   ` Bastien
2013-02-16 14:59                                   ` Eric Abrahamsen
2013-02-17  0:08                                   ` François Pinard
2013-02-18 12:57                                     ` Nicolas Richard
2013-02-18 19:17                                     ` Achim Gratz
2013-02-19  1:17                                       ` François Pinard
2013-02-16 16:40                               ` Nick Dokos [this message]
2013-02-16 16:47                                 ` Macro question with new texinfo exporter Nick Dokos
2013-02-16 16:19                           ` Nick Dokos
2013-02-16 17:37                             ` Thomas S. Dye
2013-02-04 18:10                 ` Nicolas Goaziou
2013-02-04 18:48                   ` Thomas S. Dye
2013-02-04 18:38                 ` Achim Gratz
2013-02-04 20:21                   ` Thomas S. Dye

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=7168.1361032817@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).