all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Daniel Colascione <dancol@dancol.org>, Glenn Morris <rgm@gnu.org>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Dima Kogan <dima@secretsauce.net>, 17558@debbugs.gnu.org
Subject: bug#17558: 24.4.50; global-subword-mode breaks ERC
Date: Mon, 27 Apr 2015 16:24:07 -0700 (PDT)	[thread overview]
Message-ID: <215222bf-164d-4547-af43-8d24b488c80d@default> (raw)
In-Reply-To: <553EB8A7.7070103@dancol.org>

> >> Indeed, with the new implementation of subword-mode, most of the
> >> word-operating commands should be marked as "interactive use
> >> only", since their behavior is too unreliable for use in Lisp code.
> >
> > Sounds to me like it will be a PITA to review/replace every
> > non-interactive usage of those commands.
> > Are people certain they want to go down this road?
> 
> I am. It's the only way we can make sure that interactive commands
> that move by words *indirectly* do the right thing in the presence of
> user customizations.

Mille excuses - I have not been following this thread.

Just what is meant by "non-interactive use of `forward-word'
and `backward-word'"?  Any call to either of them in Lisp code?
And what is meant by "*indirectly*".

Will you be telling users (e.g. in NEWS) precisely *how* they
need to modify existing non-interactive calls to those functions?
Saying that they should be used only interactively from now on
does not tell users how to fix existing code that calls them.

And just what is unsafe about calling these two functions from
Lisp?

Sorry, but this is not clear to me.  (And why not create new
functions/commands, instead of changing the meaning/behavior
of these longstanding ones?)

> > (At time of writing, I don't see any mention of forward-word etc
> > no longer being safe in NEWS.)
> 
> ERC is the only component I've heard of breaking. I don't think
> forward-word has *ever* been "safe" in the sense that you're
> suggesting.  Modes almost always *actually* want sexp movement.





  reply	other threads:[~2015-04-27 23:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  9:19 bug#17558: 24.4.50; global-subword-mode breaks ERC Dima Kogan
2014-05-23 20:51 ` Daniel Colascione
2014-12-31  8:46   ` Dima Kogan
2014-12-31  9:01   ` Dima Kogan
2015-01-01 16:42     ` Stefan Monnier
2015-01-01 21:47       ` Dima Kogan
2015-04-27 20:03       ` Glenn Morris
2015-04-27 22:31         ` Daniel Colascione
2015-04-27 23:24           ` Drew Adams [this message]
2015-04-27 23:30             ` Daniel Colascione
2015-04-27 23:59               ` Drew Adams
2015-04-28 16:50           ` Glenn Morris
2015-04-29  1:50             ` Stefan Monnier
2015-04-29  2:31             ` Daniel Colascione
2015-07-15  3:37               ` Dima Kogan
2015-12-26 21:46                 ` Lars Ingebrigtsen
2015-12-27 21:16                   ` Dima Kogan
2015-12-27 21:38                     ` Lars Ingebrigtsen
2016-01-08 18:54                   ` Dima Kogan
2016-01-09  9:04                     ` Lars Magne Ingebrigtsen
2016-01-09 18:14                       ` Dima Kogan
2016-01-26  8:07                         ` Dima Kogan
2016-02-04  3:21                         ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=215222bf-164d-4547-af43-8d24b488c80d@default \
    --to=drew.adams@oracle.com \
    --cc=17558@debbugs.gnu.org \
    --cc=dancol@dancol.org \
    --cc=dima@secretsauce.net \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=rgm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.