emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] C-c C-c in agenda
Date: Sat, 01 Feb 2020 21:17:10 +0100	[thread overview]
Message-ID: <84o8uif3pr.fsf@gmail.com> (raw)
In-Reply-To: CAJcAo8vQAj_vn+zL5Hez2OnmTnDDWAAxYW_fCJs_r7DEE3dRzw@mail.gmail.com

Samuel Wales <samologist@gmail.com> writes:

> i think it can be confusing to new users to have column mode
> accidentally activated.  what are the things they will try to get out
> of it?  maybe worth considering all the panic commands they'd try, and
> either deactivate or message what to do to deactivate?

Indeed.  Ease the breakout from column view was the main motivation for
the binding.

> if c-c c-c is being weighed, maybe consider it as one of those things
> to possibly tip the balance?  i do not use column mode (drawers are
> slow, too disorrganized to make a contact list with it), so cannot
> say.
>
> some things they might try are: q, c-c c-c, c-c c-k, esc esc esc, c-g,
> undo, whatever they tried last, c-u on whatever they tried last,
> revert, kill buffer, ? as a speed command, look at mode line, skim the
> manual [for what?], c-z, whatever vim does, spacemacs?.

The inspiration for the C-c C-c to quit column view was the removal of
highlightings hanging around from a sparse tree with those keys C-c C-c.

BTW C-c C-c is also a way out of the macro editing buffer.  { M-x
kmacro-edit-macro }

> similar for things like outline search view and org agenda restriction
> lock, but in my experience, those are less commonly accidentally
> activated.

I also think so for restriction lock.


Ciao,
--
Marco

  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 [this message]
2020-01-29  3:20 ` Adam Porter
2020-01-31 11:02   ` Bastien
2020-02-01 20:26   ` Marco Wahl
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=84o8uif3pr.fsf@gmail.com \
    --to=marcowahlsoft@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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).