From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Small bug in table editing
Date: Fri, 04 Feb 2011 17:58:53 +0100 [thread overview]
Message-ID: <87bp2rlos2.fsf@Rainer.invalid> (raw)
In-Reply-To: AANLkTi=uUYSmidoq28xAjfkX9Uu6V9Kx9soibR5R9AbB@mail.gmail.com
Christopher Witte <chris@witte.net.au> writes:
> I tend to disagree. I feel that anything that breaks the semantic
> model of "enter = insert new line at point" is a bug.
Then don't use org-mode tables, because "enter" has different (and at
least to me) more useful semantics there.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
next prev parent reply other threads:[~2011-02-04 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 9:40 Small bug in table editing Christopher Witte
2011-02-03 18:27 ` Achim Gratz
2011-02-04 9:04 ` Christopher Witte
2011-02-04 16:58 ` Achim Gratz [this message]
2011-02-07 9:26 ` Christopher Witte
2011-02-11 11:29 ` Bastien
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=87bp2rlos2.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).