emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: I'm tripping over #+BABEL: vs. #+PROPERTY:
Date: Thu, 15 Mar 2012 16:15:05 +0100	[thread overview]
Message-ID: <80y5r1sxom.fsf@somewhere.org> (raw)
In-Reply-To: 11652.1331760067@alphaville

Hi Nick and Eric,

Nick Dokos wrote:
> Eric Schulte <eric.schulte-KK0ffGbhmjU@public.gmane.org> wrote:
>> Did you press C-c C-c on each property line after it was written?
> Just to clarify: do I really have to C-c C-c on each line? If I add a
> bunch of them and then do C-c C-c on one of them, shouldn't that be
> enough to refresh the setup?

I got no reaction on my idea of "automagic C-c C-c" (on 2012-03-04 Sun, see

    The "automagic C-c C-c" should be NOT[1] done after each key press or some
    such. That certainly would be a killer feature, in its real acception:
    performance would be unbearable.

    In my mind, automatically (re-)parsing the meta options should be each time
    the user presses `C-c C-v C-e' (eval code blocks); that is, when the user
    expects his options to be taken into account.

Does it make sense?

Best regards,


[1] This word was missing (in the original post)!

Sebastien Vauban

  reply	other threads:[~2012-03-15 15:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 18:23 I'm tripping over #+BABEL: vs. #+PROPERTY: Ken Williams
2012-03-14 18:28 ` Eric Schulte
2012-03-14 18:32   ` Ken Williams
2012-03-14 18:39     ` Eric Schulte
2012-03-14 18:49       ` Ken Williams
2012-03-14 21:21   ` Nick Dokos
2012-03-15 15:15     ` Sebastien Vauban [this message]
2012-03-15 16:14       ` Nick Dokos
2012-03-15 16:39         ` Thomas S. Dye
2012-03-18 21:37         ` Sebastien Vauban
2012-03-19  8:21         ` Rainer M Krug

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:

  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=80y5r1sxom.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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