From: Robert Horn <rjhorn@alum.mit.edu>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Prefix arguments, checklists, and lists
Date: Sun, 03 Feb 2013 12:24:19 -0500 [thread overview]
Message-ID: <m3k3qppayk.fsf@quad.robs.office> (raw)
In-Reply-To: <87ehh99xfu.fsf@gmail.com>
Nicolas Goaziou writes:
> Hello,
>
> Robert Horn <rjhorn@alum.mit.edu> writes:
>
> As a rule of thumb, C-c C-c on a list will operate on every top level
> items and C-c C-c on a item will operate on the item. You are considered
> to be on a list when calling C-c C-c from affiliated keywords or from
> the very beginning of the first line in the first item. Note that
> element-wise navigation (like M-{ and M-}) behaves the same.
>
This is different than your initial response, and still needs to be
documented. My major concern (and the bug that Bastien fixed) was that
it was applying the whole list logic whenever the point was on the first
*item* of the list. Restricting it to being different when on the first
*character of the first item* is different, and at least allows the
commands to be used on the first line.
I still think it's poor user interface design. The impact when you go
through the documentation for each command and add "... except when on
the first character of the first item of the list, in which case the
behavior is ...." may make this clear. The user has to add that into
their thought processes when using lists. This constant side nag of
"where am I on this line? which item am I on?" is an indication of a
user interface problem.
The other times that emacs and org-mode care about where you are on the
line are situations where you are directly editing and changing the
contents of the line. It feels natural to pay attention to the location
on the line when editing the text. And, even then, the change is
restricted to that location on the line. It is only when using a
prefixed commands that the changes affect other locations.
That's why I prefer using a different prefix to mean "whole list". That
leaves all of the list related commands that affect the current item to
be C-u prefixed. If you have a different prefix that means "whole
list", you eliminate the "where is the point?" mental effort. It adds
the ability to have that different prefix enable "whole list" when on
any item in any location in the list.
R Horn
rjhorn@alum.mit.edu
next prev parent reply other threads:[~2013-02-03 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:07 Prefix arguments, checklists, and lists Robert Horn
2013-01-18 21:08 ` Nicolas Goaziou
2013-01-21 16:31 ` Robert Horn
2013-01-25 13:58 ` Nicolas Goaziou
2013-02-03 17:24 ` Robert Horn [this message]
2013-02-04 22:36 ` Nicolas Goaziou
2013-02-07 8:33 ` 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=m3k3qppayk.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).