From: Nick Dokos <nicholas.dokos@hp.com>
To: cberry@tajo.ucsd.edu
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Selectively export RESULTS
Date: Fri, 02 Mar 2012 18:01:56 -0500 [thread overview]
Message-ID: <6060.1330729316@alphaville> (raw)
In-Reply-To: Message from cberry@tajo.ucsd.edu of "Fri, 02 Mar 2012 13:35:37 PST." <874nu6it3q.fsf@tajo.ucsd.edu>
cberry@tajo.ucsd.edu wrote:
>
> I've been bitten by the 'no C-c C-c' after changing a #+property line so
> many times, you would think I'd learn. :-(
>
Yup - I don't know why, but for some reason I can see it more easily
when others do it than when I do it: I sometimes spend *minutes*
bewildered ("*how can that be?!?!*"). At some point, I get into
"Terminator" mode, go down the list for the appropriate response,
remember the C-c C-c problem, whack my head on my desk a few times, and
go on. But when next time comes, it's as if it never happened before
(well, perhaps things are improving: I generally go into "Terminator"
mode much more quickly nowadays - a couple of times in the more distant
past, I gave up in disgust, went to bed and didn't think of C-c C-c
until the next day.)
It would be so nice if org did the org-mode-restart bit automatically
after a change to a #+KEYWORD line: in some cases (e.g. TBLFM lines) you
have direct feedback so it doesn't matter too much, but in other cases,
that feedback is just nowhere to be found. I don't know how difficult it
would be to implement such a facility[fn:1], but maybe it can be added
to the GSoC list if somebody has a bright idea on how to do it.
Nick
Footnotes:
[fn:1] ... without making it too expensive to run: I wonder how
expensive it would be running org-mode-restart from an idle timer -
probably prohibitive if the file is large enough. And I can imagine
situations where that would be even *more* confusing: changing behavior
apparently without any other change - can you say magic?
next prev parent reply other threads:[~2012-03-02 23:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 5:04 Selectively export RESULTS cberry
2012-02-29 7:05 ` Thomas S. Dye
2012-02-29 16:50 ` cberry
2012-02-29 17:06 ` Eric Schulte
2012-02-29 20:24 ` cberry
2012-03-02 17:24 ` Matthew Landis
2012-03-02 17:48 ` Eric Schulte
2012-03-02 18:33 ` Matthew Landis
2012-03-02 19:33 ` Eric Schulte
2012-03-02 20:12 ` Matthew Landis
2012-03-02 20:20 ` Eric Schulte
2012-03-03 10:43 ` Sebastien Vauban
2012-03-03 14:52 ` Achim Gratz
2012-03-03 23:01 ` Sebastien Vauban
2012-03-04 10:37 ` Achim Gratz
2012-03-04 20:44 ` Sebastien Vauban
2012-03-02 19:42 ` cberry
2012-03-02 20:26 ` Eric Schulte
2012-03-02 21:08 ` cberry
2012-03-02 21:26 ` Nick Dokos
2012-03-02 21:35 ` cberry
2012-03-02 23:01 ` Nick Dokos [this message]
2012-03-02 17:59 ` Christophe Pouzat
2012-03-02 18:53 ` Matthew Landis
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=6060.1330729316@alphaville \
--to=nicholas.dokos@hp.com \
--cc=cberry@tajo.ucsd.edu \
--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).