emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: A Microsoftesque detail in org
Date: Sun, 17 May 2015 23:24:47 +0300	[thread overview]
Message-ID: <87k2w754vk.fsf@iki.fi> (raw)
In-Reply-To: 87lhgqxeq0.fsf@gmx.us


Rasmus <rasmus@gmx.us> writes:

Greetings Rasmus.

>> 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.
>
> I disagree.  Consider the more complete example:
>
> * TODO [#A] foo bar        :tag:
>
> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
> (iii) break the tag.  At least (i) and (ii) are quite destructive.

I am not sure what you mean, since a single undo will always heal the
line again, regardless of where you break it.

I am a BIG fan of the Org mode slogan "Your life in plain text." The
power of plain text has been demonstrated over and over again. You can
run text manipulating commands on it, you can process it with a large
array of different programming languages.

An undo is a basic text editing feature that everyone should
know. Reassigning non-standard behaviour to the return key is - in my
opinion - against the ideology.

> The attached patch re-enables breaks in region four of
> org-complex-heading-regexp, i.e. from the cookie up to tags.  A quick
> test suggests it works nicely.
>
> WDYT?

Given enough time, I could come up with a situation where I would run a
keyboard macro in which I would expect the return key to break the line,
regardless of where I was on that line (in a tag or whatever).

I am a very minor player in this game, but I would really, _really_ like
Org to remain as true to it's slogan as possible.

Keeping it real,

Jarmo

  parent reply	other threads:[~2015-05-17 20:25 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 [this message]
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
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=87k2w754vk.fsf@iki.fi \
    --to=jarmo.hurri@iki.fi \
    --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).