From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: possible bug: TAB after elipsis
Date: Sat, 27 Mar 2010 19:53:58 +0000 (UTC) [thread overview]
Message-ID: <87d3ypd0fn.fsf@mean.albasani.net> (raw)
In-Reply-To: a037f7361003271221w1d7dcd8ep4cb5c4d0c1720915@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
> This awesome. If this equivalent existed for M-a/e and M-f/b, I would
> be very happy with the result. Seem reasonable -- when on a folded
> headline, I just can't think of a reason someone would want to
> interact with the headline after the ellipsis. It even, as someone
> else mentioned, can ge one into trouble -- press the wrong key or
> delete after it and you're removing text you can't even see... but are
> able to interact with!
Well, after all, its just "Plain Text" you are editing.
Whenever there is an Elipsis, there is a convenient "hack" in the
display hiding what you don't want to see, but it is never the less a
hack. So I got into the habbit that, whenever I edit a line that
contains "...", I unfold it first; whenever it is folded, I only
a ) view it or
b) navigate with the org commands like the speed keys
(http://orgmode.org/manual/Speed-keys.html) or
c) use the org structure editing command
(http://orgmode.org/manual/Structure-editing.html).
For extensive editing with emacs board tools, there is always
"M-x show-all".
So, I agree, whenever there are ellipsis, editing "it ... can
get one into trouble". So I just don't ;).
hth
Memnon
next prev parent reply other threads:[~2010-03-27 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 18:04 possible bug: TAB after elipsis Anthony Lander
2010-03-26 5:50 ` Livin Stephen Sharma
2010-03-26 6:32 ` Carsten Dominik
2010-03-26 9:25 ` Ben Finney
2010-03-26 9:38 ` peter.frings
2010-03-26 17:23 ` John Hendy
2010-03-27 16:35 ` Anthony Lander
2010-03-27 19:02 ` Memnon Anon
2010-03-27 19:21 ` John Hendy
2010-03-27 19:53 ` Memnon Anon [this message]
2010-03-27 20:02 ` John Hendy
2010-03-27 23:26 ` Bernt Hansen
2010-03-27 23:29 ` Bernt Hansen
2010-03-28 11:45 ` Alan E. Davis
2010-03-28 11:58 ` Carsten Dominik
2010-03-28 13:25 ` Alan E. Davis
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=87d3ypd0fn.fsf@mean.albasani.net \
--to=gegendosenfleisch@googlemail.com \
--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).