emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-orgmode@gnu.org
Subject: 45048eb78359fc742097982fc1adc5ca5e4b2509 Fix `C-e' with visible lines and arguments
Date: Sat, 29 Apr 2017 15:25:11 -0400	[thread overview]
Message-ID: <bbecaf09-2ff1-ce37-04df-bbe3e1f7328d@gmail.com> (raw)

Hi all,

Commit 45048eb78359fc742097982fc1adc5ca5e4b2509 (Fix `C-e' with visible lines and arguments, http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=45048eb78359fc742097982fc1adc5ca5e4b2509) breaks my usual org-mode workflow, in which I commonly press C-e to go past the ellipses of a folded headline and press M-S-RET to insert a new TODO item.  With the change, C-e M-S-RET now moves the body of the current todo entry below the new todo header.

It used to be the case that C-e moved past ellipses, which made it very easy to insert a new TODO item below the current one.  Is there an easy way to do the same thing now that C-e leaves the point before ellipses?  C-u C-u M-S-RET inserts at the end of the current list, unfortunately.  

I realize that the change in behavior isn't an accident (the commit updated the docstring to say "Go to the end of the line, but before ellipsis, if any."), but I'm curious to know whether I was doing something wrong before, and whether there is a simple way to achieve the behavior I described now (short of flet-ing end-of-line to end-of-visual-line around calls to org-end-of-line).

Thanks!
Clément.

             reply	other threads:[~2017-04-29 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 19:25 Clément Pit-Claudel [this message]
2017-04-30 20:28 ` 45048eb78359fc742097982fc1adc5ca5e4b2509 Fix `C-e' with visible lines and arguments Nicolas Goaziou
2017-04-30 21:29   ` Clément Pit-Claudel

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=bbecaf09-2ff1-ce37-04df-bbe3e1f7328d@gmail.com \
    --to=cpitclaudel@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).