emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Babel, Python and UTF-8
Date: Mon, 6 Dec 2010 08:40:40 -1000	[thread overview]
Message-ID: <D297E7DA-57E1-4987-A580-81A35C3929B0@tsdye.com> (raw)
In-Reply-To: <87r5du93n7.fsf@Rainer.invalid>


On Dec 6, 2010, at 8:07 AM, Achim Gratz wrote:

> "Thomas S. Dye" <tsd@tsdye.com> writes:
>> Emacs configuration is one of the highest barriers to entry for
>> potential adopters of Org-mode, IMO.  The idea of context-sensitive
>> configuration is potentially terrific.  It gets the user to work more
>> quickly than would otherwise be the case.  The problem I've run into
>> is that exiting a buffer doesn't change the configuration back to  
>> some
>> initial, or base, state.  I'm on to the next task but still  
>> configured
>> to do the last thing.
>
> Isn't that what buffer-local variables are for?
>
>
> Achim.
> -- 
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
> http://Synth.Stromeko.net/Downloads.html#KorgSDada
>
>

Aloha Achim,

I suppose so, but AFAIK I haven't seen them in the configuration code  
blocks that Dan mentioned.  I might be missing something.

I experimented with buffer-local configuration variables myself a  
while back, but my Lisp skills are sub-minimal and I couldn't make  
them work to my satisfaction.

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

  reply	other threads:[~2010-12-06 18:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 23:50 Babel, Python and UTF-8 Vincent Beffara
2010-12-02  1:18 ` Eric Schulte
2010-12-02  1:36   ` Vincent Beffara
2010-12-02  9:11     ` Sébastien Vauban
2010-12-02 19:34       ` Eric Schulte
2010-12-02 20:10         ` Sébastien Vauban
2010-12-03 10:27           ` Vincent Beffara
2010-12-03 11:27             ` Sébastien Vauban
2010-12-03 14:30             ` Eric Schulte
2010-12-03 15:43               ` Vincent Beffara
2010-12-05 15:30                 ` Eric Schulte
2010-12-06  9:42                   ` Dan Davison
2010-12-06 11:53                     ` Eric S Fraga
2010-12-06 16:42                     ` Thomas S. Dye
2010-12-06 18:07                       ` Achim Gratz
2010-12-06 18:40                         ` Thomas S. Dye [this message]
2010-12-06 18:23                       ` Dan Davison
2010-12-02 14:29     ` Eric Schulte
2010-12-02 16:12       ` Vincent Beffara
2010-12-02 18:23       ` Dan Davison
2010-12-02 19:36         ` Eric Schulte
2010-12-02 20:05           ` Sébastien Vauban
2010-12-02 16:09     ` Sébastien Vauban
2010-12-02 16:44       ` Vincent Beffara
2010-12-03 14:56         ` Christopher Allan Webber

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=D297E7DA-57E1-4987-A580-81A35C3929B0@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=Stromeko@nexgo.de \
    --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).