unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* RE: C-o
@ 2024-07-02 15:41 Drew Adams
  2024-07-02 15:47 ` C-o Daniel Colascione
  2024-07-02 16:20 ` C-o Dr. Arne Babenhauserheide
  0 siblings, 2 replies; 9+ messages in thread
From: Drew Adams @ 2024-07-02 15:41 UTC (permalink / raw)
  To: Dmitry Gutov, Stefan Monnier, Po Lu
  Cc: Daniel Colascione, Alan Mackenzie, Stefan Kangas,
	emacs-devel@gnu.org

> >>> What do you use it for?
> > I'm also curious to know how people use `C-o`, which I never ever use.

I wasn't going to chime in on this thread...

My use of `C-o' is, well, peculiar.  I almost
don't use it.

I keep its default binding, which I never use
it for.  I use it only to try/test a command
I want to temporarily bind to a repeatable,
simple key that won't interfere with bindings
I really do use.  I do this (fairly often):

 M-x global-set-key RET C-o <some command
 I want to use temporarily, perhaps repeatedly
 (by just holding it down)> RET

Yeah, I know, seems a waste of such a simple,
repeatable key.  But it's precisely the
uselessness to me of that binding that keeps
the key free for me mentally.  In effect, I've
unconsciously tossed it onto the No-Default
Free List.

Needless to say, I do NOT want its default
binding to be changed to some command that's
useful but not repeatable.

I dread this thread, given that it has the
possibility that Emacs will change the useless
binding of `C-o' to some command that's useful
but not repeatable.  (Repeatable keys not at
the end of a prefix key are indeed rare).

IOW, it's a bad default binding, but therein
lies its usefulness: it could be worse.

[ The only reasonable alternative to binding a
  simple repeatable key to a repeatable command
  is to bind it as a prefix key.  That's what
  we've done for keys such as `C-x'.  That's
  OK.  But to bind a simple repeatable key to a
  command that, e.g., prompts for something is
  a mortal sin. Thou Shalt Not Waste. ]

  - Church of Emacs

I was content to let this sleeping dog lie.
Now that it's awakened, Bonjour les dégats...


^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: C-o
  2024-07-02 15:41 C-o Drew Adams
@ 2024-07-02 15:47 ` Daniel Colascione
  2024-07-02 17:18   ` C-o Alfred M. Szmidt
  2024-07-02 16:20 ` C-o Dr. Arne Babenhauserheide
  1 sibling, 1 reply; 9+ messages in thread
From: Daniel Colascione @ 2024-07-02 15:47 UTC (permalink / raw)
  To: Drew Adams, Dmitry Gutov, Stefan Monnier, Po Lu
  Cc: Alan Mackenzie, Stefan Kangas, emacs-devel@gnu.org



On July 2, 2024 11:41:55 AM EDT, Drew Adams <drew.adams@oracle.com> wrote:
>> >>> What do you use it for?
>> > I'm also curious to know how people use `C-o`, which I never ever use.
>
>I wasn't going to chime in on this thread...
>
>My use of `C-o' is, well, peculiar.  I almost
>don't use it.
>
>I keep its default binding, which I never use
>it for.  I use it only to try/test a command
>I want to temporarily bind to a repeatable,
>simple key that won't interfere with bindings
>I really do use.  I do this (fairly often):
>
> M-x global-set-key RET C-o <some command
> I want to use temporarily, perhaps repeatedly
> (by just holding it down)> RET
>
>Yeah, I know, seems a waste of such a simple,
>repeatable key.  But it's precisely the
>uselessness to me of that binding that keeps
>the key free for me mentally.  In effect, I've
>unconsciously tossed it onto the No-Default
>Free List.
>
>Needless to say, I do NOT want its default
>binding to be changed to some command that's
>useful but not repeatable.
>
>I dread this thread, given that it has the
>possibility that Emacs will change the useless
>binding of `C-o' to some command that's useful
>but not repeatable.  (Repeatable keys not at
>the end of a prefix key are indeed rare).


If the default binding for C-o changed, how would your workflow change? Are you imagining we'd bind C-o to some *new* functionality for which we didn't have other bindings, forcing you to forego this functionality, change your habits, or bind the new functionality to some other key yourself?

>
>IOW, it's a bad default binding, but therein
>lies its usefulness: it could be worse.
>
>[ The only reasonable alternative to binding a
>  simple repeatable key to a repeatable command
>  is to bind it as a prefix key.  That's what
>  we've done for keys such as `C-x'.  That's
>  OK.  But to bind a simple repeatable key to a
>  command that, e.g., prompts for something is
>  a mortal sin. Thou Shalt Not Waste. ]
>
>  - Church of Emacs
>
>I was content to let this sleeping dog lie.
>Now that it's awakened, Bonjour les dégats...
>



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 15:41 C-o Drew Adams
  2024-07-02 15:47 ` C-o Daniel Colascione
@ 2024-07-02 16:20 ` Dr. Arne Babenhauserheide
  1 sibling, 0 replies; 9+ messages in thread
From: Dr. Arne Babenhauserheide @ 2024-07-02 16:20 UTC (permalink / raw)
  To: Drew Adams
  Cc: Dmitry Gutov, Stefan Monnier, Po Lu, Daniel Colascione,
	Alan Mackenzie, Stefan Kangas, emacs-devel@gnu.org

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

Drew Adams <drew.adams@oracle.com> writes:

>> >>> What do you use it for?
>> > I'm also curious to know how people use `C-o`, which I never ever use.
>
> I wasn't going to chime in on this thread...

I regularly use C-o. It’s pretty useful to add newlines without
automation which cuts in on pressing Enter.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 15:47 ` C-o Daniel Colascione
@ 2024-07-02 17:18   ` Alfred M. Szmidt
  2024-07-02 17:52     ` C-o Stefan Monnier
  2024-07-02 18:27     ` C-o Eli Zaretskii
  0 siblings, 2 replies; 9+ messages in thread
From: Alfred M. Szmidt @ 2024-07-02 17:18 UTC (permalink / raw)
  To: Daniel Colascione
  Cc: drew.adams, dmitry, monnier, luangruo, acm, stefankangas,
	emacs-devel

Seeing how hard it is to agree on adding a new keybinding where none
exist, can we not descend into madness where we fload ideas to modifiy
things that have existed in Emacs since TECO days -- suggesting to
modify C-o is a hornets nest that one shouldn't touch.



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 17:18   ` C-o Alfred M. Szmidt
@ 2024-07-02 17:52     ` Stefan Monnier
  2024-07-02 18:56       ` [External] : C-o Drew Adams
  2024-07-02 22:12       ` C-o Daniel Colascione
  2024-07-02 18:27     ` C-o Eli Zaretskii
  1 sibling, 2 replies; 9+ messages in thread
From: Stefan Monnier @ 2024-07-02 17:52 UTC (permalink / raw)
  To: Alfred M. Szmidt
  Cc: Daniel Colascione, drew.adams, dmitry, luangruo, acm,
	stefankangas, emacs-devel

> Seeing how hard it is to agree on adding a new keybinding where none
> exist, can we not descend into madness where we fload ideas to modifiy
> things that have existed in Emacs since TECO days -- suggesting to
> modify C-o is a hornets nest that one shouldn't touch.

To clarify: I started this `C-o` subthread for the sole purpose of
understanding what I'm missing.  I have no intention to change the `C-o`
binding (I'd even argue it's good to keep such a short "useless" binding
around since it acts as a kind of "user-reserved" key).


        Stefan




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 17:18   ` C-o Alfred M. Szmidt
  2024-07-02 17:52     ` C-o Stefan Monnier
@ 2024-07-02 18:27     ` Eli Zaretskii
  1 sibling, 0 replies; 9+ messages in thread
From: Eli Zaretskii @ 2024-07-02 18:27 UTC (permalink / raw)
  To: Alfred M. Szmidt
  Cc: dancol, drew.adams, dmitry, monnier, luangruo, acm, stefankangas,
	emacs-devel

> From: "Alfred M. Szmidt" <ams@gnu.org>
> Cc: drew.adams@oracle.com, dmitry@gutov.dev, monnier@iro.umontreal.ca,
>  luangruo@yahoo.com, acm@muc.de, stefankangas@gmail.com, emacs-devel@gnu.org
> Date: Tue, 02 Jul 2024 13:18:34 -0400
> 
> Seeing how hard it is to agree on adding a new keybinding

It isn't hard, at least not in this case.  You just sometimes need to
ignore messages posted here that don't affect the actual
decision-making process.

> can we not descend into madness where we fload ideas to modifiy
> things that have existed in Emacs since TECO days -- suggesting to
> modify C-o is a hornets nest that one shouldn't touch.

Don't worry, C-o will not be changed any time soon.  People can talk
all they want, it's a free forum.




^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: [External] : Re: C-o
  2024-07-02 17:52     ` C-o Stefan Monnier
@ 2024-07-02 18:56       ` Drew Adams
  2024-07-02 22:12       ` C-o Daniel Colascione
  1 sibling, 0 replies; 9+ messages in thread
From: Drew Adams @ 2024-07-02 18:56 UTC (permalink / raw)
  To: Stefan Monnier, Alfred M. Szmidt
  Cc: Daniel Colascione, dmitry@gutov.dev, luangruo@yahoo.com,
	acm@muc.de, stefankangas@gmail.com, emacs-devel@gnu.org

> (I'd even argue it's good to keep such a short "useless" binding
> around since it acts as a kind of "user-reserved" key).

Great minds think alike. ;-)



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 17:52     ` C-o Stefan Monnier
  2024-07-02 18:56       ` [External] : C-o Drew Adams
@ 2024-07-02 22:12       ` Daniel Colascione
  2024-07-03  1:49         ` C-o Stefan Monnier
  1 sibling, 1 reply; 9+ messages in thread
From: Daniel Colascione @ 2024-07-02 22:12 UTC (permalink / raw)
  To: Stefan Monnier
  Cc: Alfred M. Szmidt, drew.adams, dmitry, luangruo, acm, stefankangas,
	emacs-devel

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Seeing how hard it is to agree on adding a new keybinding where none
>> exist, can we not descend into madness where we fload ideas to modifiy
>> things that have existed in Emacs since TECO days -- suggesting to
>> modify C-o is a hornets nest that one shouldn't touch.
>
> To clarify: I started this `C-o` subthread for the sole purpose of
> understanding what I'm missing.  I have no intention to change the `C-o`
> binding (I'd even argue it's good to keep such a short "useless" binding
> around since it acts as a kind of "user-reserved" key).

Same here.  It might also be useful to think about whether open-line can
be made more useful or DWIM-y in a way that doesn't break compatibility.



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: C-o
  2024-07-02 22:12       ` C-o Daniel Colascione
@ 2024-07-03  1:49         ` Stefan Monnier
  0 siblings, 0 replies; 9+ messages in thread
From: Stefan Monnier @ 2024-07-03  1:49 UTC (permalink / raw)
  To: Daniel Colascione
  Cc: Alfred M. Szmidt, drew.adams, dmitry, luangruo, acm, stefankangas,
	emacs-devel

> Same here.  It might also be useful to think about whether open-line can
> be made more useful or DWIM-y in a way that doesn't break compatibility.

Many people mentioned the use of `C-o` specifically because it's not as
DWIMish as RET, so it sounds like it's probably better to leave
it alone.


        Stefan




^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2024-07-03  1:49 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-02 15:41 C-o Drew Adams
2024-07-02 15:47 ` C-o Daniel Colascione
2024-07-02 17:18   ` C-o Alfred M. Szmidt
2024-07-02 17:52     ` C-o Stefan Monnier
2024-07-02 18:56       ` [External] : C-o Drew Adams
2024-07-02 22:12       ` C-o Daniel Colascione
2024-07-03  1:49         ` C-o Stefan Monnier
2024-07-02 18:27     ` C-o Eli Zaretskii
2024-07-02 16:20 ` C-o Dr. Arne Babenhauserheide

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).