From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: possible bug: TAB after elipsis
Date: Sat, 27 Mar 2010 19:02:03 +0000 (UTC) [thread overview]
Message-ID: <87sk7ld26n.fsf@mean.albasani.net> (raw)
In-Reply-To: F6549627-4B91-44A6-B9FC-B3E10A3C8753@yahoo.com
Anthony Lander <anthonylander@yahoo.com> writes:
> I was thinking about this a bit more. Is it possible to meet in the
> middle and restrict the cursor so that it can't go past the last
> character in the headline, like this:
>
> *** Some entry|...
>
> I suggest this because if you do type after the elipsis, the text goes
> right on the end of the folded entry, which I believe is undesirable as
> well; It means that part of the entry is invisible, and part is
> visible. Limiting the cursor would solve both problems. Is this even
> feasible?
I have not been following closely this thread, but I believe customizing
"org-special-ctrl-a/e" might bring you a long way towards the behaviour
you want. I suggest you give it a try.
,----[ (info "(org)Headlines") ]
| Documentation:
| Non-nil means `C-a' and `C-e' behave specially in headlines and items.
|
| When t, `C-a' will bring back the cursor to the beginning of the
| headline text, i.e. after the stars and after a possible TODO keyword.
| In an item, this will be the position after the bullet.
| When the cursor is already at that position, another `C-a' will bring
| it to the beginning of the line.
|
| `C-e' will jump to the end of the headline, ignoring the presence of tags
| in the headline. A second `C-e' will then jump to the true end of the
| line, after any tags. This also means that, when this variable is
| non-nil, `C-e' also will never jump beyond the end of the heading of a
| folded section, i.e. not after the ellipses.
`----
hth
memnon
next prev parent reply other threads:[~2010-03-27 19:02 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 [this message]
2010-03-27 19:21 ` John Hendy
2010-03-27 19:53 ` Memnon Anon
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=87sk7ld26n.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).