From: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Configuration query
Date: Thu, 18 Nov 2010 15:03:47 +0100 [thread overview]
Message-ID: <4CE53243.10309@unibas.ch> (raw)
In-Reply-To: <B53450B7-6C7F-4E06-97FE-83F871FF6A54@tsdye.com>
M-x load-file RET .emacs ?
On 11/17/10 10:19 PM, Thomas S. Dye wrote:
> Aloha all,
>
> This might be a naive query, but I'm wondering if there is some standard
> way to put the emacs configuration back to a previous state outside of
> the customization interface?
>
> I'm finding that I frequently work with Org-mode files that need
> different configurations. I typically have a #+begin_src emacs-lisp
> block in these files that I can execute with C-c C-c, so that emacs
> behaves the way the file requires for the task at hand. When I'm done,
> though, and jump onto the next task, which might depend on my standard
> configuration to work correctly, I sometimes find that the changes I've
> made break things. At this point, I typically save, quit emacs and start
> over.
>
> What I'd like to do is be able to have, in each file that contains an
> emacs-lisp source block that changes the configuration, a corresponding
> source code block that puts things back the way they were before the
> block was executed.
>
> Perhaps there is an easy way to do this?
>
> All the best,
> Tom
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-11-18 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 21:19 Configuration query Thomas S. Dye
2010-11-18 9:47 ` Sébastien Vauban
2010-11-18 14:03 ` Jörg Hagmann [this message]
2010-11-18 16:43 ` Thomas S. Dye
2010-11-18 17:42 ` Sébastien Vauban
2010-11-18 22:07 ` Nicolas Goaziou
2010-11-18 22:38 ` 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=4CE53243.10309@unibas.ch \
--to=joerg.hagmann@unibas.ch \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).