From: tsd@tsdye.com (Thomas S. Dye)
To: Titus von der Malsburg <malsburg@posteo.de>
Cc: Jarmo Hurri <jarmo.hurri@iki.fi>, emacs-orgmode@gnu.org
Subject: Re: A Microsoftesque detail in org
Date: Fri, 15 May 2015 10:27:09 -1000 [thread overview]
Message-ID: <m2zj55fuxu.fsf@tsdye.com> (raw)
In-Reply-To: <87oallabby.fsf@posteo.de> (Titus von der Malsburg's message of "Fri, 15 May 2015 12:29:37 -0700")
I like this feature and hope that I can keep it by setting a variable if
changes are made.
All the best,
Tom
Titus von der Malsburg <malsburg@posteo.de> writes:
> I fully agree with this, I find this “feature” very irritating. There
> is a strong expectation that hitting enter inserts a line break
> at the position of the cursor. Can we please stick to that?
>
> When I put the cursor in the middle of a word and press enter that also
> “breaks” the word. Yet we would not prevent the user from doing this.
>
> Titus
>
> On 2015-05-15 Fri 02:35, Jarmo Hurri wrote:
>> Greetings.
>>
>> I was just amazed by the following detail in org. In the example below,
>> if my cursor is anywhere inside the word "Example", and I press Enter, a
>> new line will be inserted below, and the cursor will jump to the next
>> line. The location of the cursor inside the heading line is ignored, and
>> the heading line will not be broken.
>>
>> # --------------------------------------------------------------------
>> * Example
>> Some text.
>> # --------------------------------------------------------------------
>>
>> This immediately reminded me of Microsoft products, where the software
>> tries to be too intelligent, thus making it harder for the user. In this
>> case, I needed to figure out that Ctrl-o is needed to break the line.
>>
>> I would suggest that the original interpretation of Enter would not be
>> messed with. Messing with Alt-Enter and such is fine, but Enter, please
>> no.
>>
>> Or?
>>
>> Jarmo
>
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-05-15 20:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 9:35 A Microsoftesque detail in org Jarmo Hurri
2015-05-15 9:57 ` Rainer M Krug
2015-05-15 11:16 ` Doug Lewan
2015-05-15 11:27 ` Rasmus
2015-05-16 8:05 ` Nicolas Goaziou
2015-05-16 15:28 ` Rasmus
2015-05-16 17:26 ` Titus von der Malsburg
2015-05-16 19:00 ` Rasmus
2015-05-16 21:43 ` Titus von der Malsburg
2015-05-17 13:25 ` Rasmus
2015-05-17 20:24 ` Jarmo Hurri
2015-05-17 21:15 ` Rasmus
2015-05-18 0:39 ` Titus von der Malsburg
2015-05-18 3:40 ` Thomas S. Dye
2015-05-18 12:15 ` Jarmo Hurri
2015-05-18 8:33 ` Brett Witty
2015-05-18 9:02 ` Rainer M Krug
2015-05-18 9:48 ` Rasmus
2015-05-18 11:29 ` Rainer M Krug
2015-05-18 13:07 ` William Denton
2015-05-18 14:37 ` Suvayu Ali
2015-05-18 15:39 ` Rasmus
2015-05-19 9:39 ` Suvayu Ali
2015-05-20 23:04 ` Rasmus
2015-05-15 19:29 ` Titus von der Malsburg
2015-05-15 20:27 ` Thomas S. Dye [this message]
2015-05-16 3:43 ` Bob Newell
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=m2zj55fuxu.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
--cc=malsburg@posteo.de \
/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).