unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 10387@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#10387: CODE wishlist: search-prop.el
Date: Sun, 24 Nov 2013 09:49:37 -0800 (PST)	[thread overview]
Message-ID: <4d7fd2ab-f511-4092-99e4-d5c848210f99@default> (raw)
In-Reply-To: <<83vbzhbugs.fsf@gnu.org>>

> > > > emacs -Q   ; or emacs -Q -nw
> > >
> > > The difference is important here.
> >
> > What difference?  And what importance?
> > Use either one in the recipe.
> > Same effect wrt using `C-M-~', AFAICT.
> > `emacs -Q -nw' has the behavior I reported, as does
> > `emacs -Q'.  (At least on MS Windows.)
>                 ^^^^^^^^^^^^^^^^^^^^^^
> Actually, _only_ on MS-Windoes.  (Well, on MS-DOS as well,
> but who cares?)

Got it.  Thx.  Perhaps I will change that default binding,
with that knowledge.

At any rate, I was explaining why I chose that key sequence.

Which key to use is not really the point of my post about
`isearch-prop.el'.  The toggle key to use is only a bike shed.
Paint it any color you like.





       reply	other threads:[~2013-11-24 17:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<87wr9h2kju.fsf@cante.cante.net>
     [not found] ` <<4e9dd7b9-9109-4f67-a9a2-d3c13635c566@default>
     [not found]   ` <<87eh664rrr.fsf@mail.jurta.org>
     [not found]     ` <<c05a5e24-a7be-4a23-9698-814b611e46e0@default>
     [not found]       ` <<878uwe62ae.fsf@igel.home>
     [not found]         ` <<7b510b39-00e7-49f6-a1ee-114652fd701c@default>
     [not found]           ` <<jwvfvqlwy23.fsf-monnier+emacsbugs@gnu.org>
     [not found]             ` <<dee893b9-9538-46ce-9c8e-18468026da14@default>
     [not found]               ` <<83vbzhbugs.fsf@gnu.org>
2013-11-24 17:49                 ` Drew Adams [this message]
2011-12-28  7:59 bug#10387: CODE wishlist: search-prop.el Jari Aalto
2012-04-12 20:07 ` Lars Magne Ingebrigtsen
2012-04-12 21:55   ` Stefan Monnier
2012-04-13  3:29     ` Michael Olson
2012-04-13 13:03       ` Stefan Monnier
2016-02-25  6:29         ` Lars Ingebrigtsen
2016-02-25 14:55           ` Drew Adams
2019-06-27 15:47   ` Lars Ingebrigtsen
2013-11-23 17:35 ` Drew Adams
2013-11-23 23:34   ` Juri Linkov
2013-11-24  0:00     ` Drew Adams
2013-11-24  1:01       ` Andreas Schwab
2013-11-24  1:07         ` Drew Adams
2013-11-24 11:36           ` Andreas Schwab
2013-11-24 16:51             ` Drew Adams
2013-11-24 17:04               ` Eli Zaretskii
2013-11-25  3:20                 ` Stefan Monnier
2013-11-25  9:55                   ` Andreas Schwab
2013-11-24 17:17               ` Andreas Schwab
2013-11-24 16:43           ` Stefan Monnier
2013-11-24 16:54             ` Drew Adams
2013-11-24 17:06               ` Eli Zaretskii

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=4d7fd2ab-f511-4092-99e4-d5c848210f99@default \
    --to=drew.adams@oracle.com \
    --cc=10387@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=schwab@linux-m68k.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.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).