From: Wanrong Lin <wanrong.lin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: return key does not show the subtree the first time on a newly opened org file
Date: Thu, 28 Feb 2008 10:31:47 -0500 [thread overview]
Message-ID: <47C6D3E3.8070706@gmail.com> (raw)
In-Reply-To: <87lk55ctff.fsf@bzg.ath.cx>
Bastien Guerry wrote:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>
>>> Yes, but only with this setting will <return> key be added to the
>>> "org-mouse-map" key map, and be bound to "org-open-at-point" command
>>> under certain contexts (like on the leading stars of a heading).
>>> Further, "org-open-at-point" is advised by org-mouse.el, which will
>>> do "org-cycle" under certain contexts.
>>>
>> Yes, this is really an accidental feature by a sequence of events:
>>
>> org-return-follow-link will add org-return to the mouse-map
>> org-mouse.el will activate the stars in a headline
>>
>
> Yes, there is an advice for this in org-mouse.el.
>
> I think we should remove it since org-mouse.el shouldn't change the
> behavior of keystrokes (only the behavior of the mouse.)
>
>
That probably is true. But I have doubt that removing the advice itself
and bind the key in some other place will really solve the problem. To
me, it seems somehow the first time you open a org-file, some context is
not recognized correctly and hence the key map is not activated. If I
just execute a command, any command (like "C-g" which does nothing), and
then press the return key, it will work. Is that puzzling? :-)
Wanrong
next prev parent reply other threads:[~2008-02-28 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 16:59 Bug: return key does not show the subtree the first time on a newly opened org file Wanrong Lin
2008-02-27 17:14 ` Wanrong Lin
2008-02-28 1:38 ` Bastien
2008-02-28 2:16 ` Wanrong Lin
2008-02-28 6:42 ` Carsten Dominik
2008-02-28 9:38 ` Bastien Guerry
2008-02-28 15:31 ` Wanrong Lin [this message]
2008-02-29 1:21 ` Bastien Guerry
2008-02-29 2:25 ` Wanrong Lin
2008-02-28 20:09 ` Wanrong Lin
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=47C6D3E3.8070706@gmail.com \
--to=wanrong.lin@gmail.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).