From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: A Microsoftesque detail in org
Date: Mon, 18 May 2015 15:15:39 +0300 [thread overview]
Message-ID: <87twvarsic.fsf@iki.fi> (raw)
In-Reply-To: 87k2w6d8ii.fsf@posteo.de
Titus von der Malsburg <malsburg@posteo.de> writes:
> On 2015-05-17 Sun 14:15, Rasmus wrote:
>>>> 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.
>>
>> Sure. But that seems orthogonal to the problem at hand. Re (i): Assume
>> TODO is keyword. We don't know that TO is. Re (ii): [#B] is a cookie.
>> [#B is not. (iii) iii :tag: is a tag :ta is not. The editor should not
>> easily produce invalid syntax.
>
> I disagree with that last statement. I’m not aware of any Emacs mode
> (or any other text editor for that matter) that prevents me from
> producing invalid syntax. A text editor preventing invalid syntax is
> actually not even desirable because the path from one syntactically
> valid state of the document to the next often leads through invalid
> states. If you really want to prevent temporarily invalid documents,
> the result is going to be some kind of GUI application, not a text
> editor. While that may be a valid solution for some people, it is
> certainly not the Emacs way of doing things.
Exactly!
I would prefer that by default there is no "intelligence" in the return
key, but more intelligence can be added as an option. (The problem with
Microsoft programs is exactly the fact that too much "intelligence" is
the default.)
I leave it to the wiser men to decide. Over and out from me.
Jarmo
next prev parent reply other threads:[~2015-05-18 12:16 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 [this message]
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=87twvarsic.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).