From: Marco Wahl <marcowahlsoft@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] C-c C-c in agenda
Date: Sat, 01 Feb 2020 21:26:35 +0100 [thread overview]
Message-ID: <84imkqf3po.fsf@gmail.com> (raw)
In-Reply-To: 87eevjgd85.fsf@alphapapa.net
Hi Adam,
Adam Porter <adam@alphapapa.net> writes:
>> For some days now C-c C-c disables column view in Org files. This helps
>> me a bit and never got in my way. And I thought it would be quite
>> natural and consistent to use this binding for the agenda too.
>>
>> What do you think about all that?
>
> Hi Marco,
>
> I've always had the impression that the "C-c C-c" binding was intended
> to do the most obviously useful or natural action in the current
> context. For example, in a capture or log buffer, it completes the
> capture. With point on a #+ line, it resets buffer properties
> accordingly.
>
> I don't use column view very often, so I may be biased, but anyway: in
> the general context of an Agenda buffer, I don't feel like enabling or
> disabling column view is the most obviously useful or natural thing to
> do, so "C-c C-c" doesn't seem like an appropriate binding to me.
Yes, it might not be 100% natural.
But as Samuel pointed out accidentially turned on column view can be a
trap in particular for new users. And C-c C-c often is a way out not
only in Org mode. And also recall Bastien's observation that C-c C-c
already all the time quit column view when triggered on a line in column
view state.
Best regards,
--
Marco
next prev parent reply other threads:[~2020-02-01 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 9:20 [RFC] C-c C-c in agenda Marco Wahl
2020-01-28 11:17 ` Bastien
2020-01-28 11:48 ` Bastien
2020-01-28 12:46 ` Marco Wahl
2020-01-28 12:54 ` Bastien
2020-01-28 13:16 ` Marco Wahl
2020-01-28 14:07 ` Bastien
2020-01-28 14:19 ` Bastien
2020-01-28 14:50 ` Marco Wahl
2020-01-28 19:32 ` Samuel Wales
2020-02-01 20:17 ` Marco Wahl
2020-01-29 3:20 ` Adam Porter
2020-01-31 11:02 ` Bastien
2020-02-01 20:26 ` Marco Wahl [this message]
2020-02-01 21:54 ` Samuel Wales
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=84imkqf3po.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=adam@alphapapa.net \
--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).