unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16493@debbugs.gnu.org
Subject: bug#16493: 24.3.50; (setq search-invisible t) is useless, let's allow to turn visible-mode temporarily on
Date: Tue, 21 Jan 2014 15:20:34 +0100	[thread overview]
Message-ID: <87k3dtl8lp.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwvd2jl4f07.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 21 Jan 2014 08:54:56 -0500")

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

>> E.g. replacing "www" by "ftp" is currently not possible in
>>   [[http://gnu.org][GNU]]
>> you have to manually turn visible-mode on.
>
> I don't understand the relationship between this problem and the subject
> of bug#16493.

I forgot to connect the dots.

When search-invisible is t, perform-replace can replace matches
in any invisible text, but does not display it when prompting the
user for confirmation.

When search-invisible is 'open, perform-replace can replace matches
only in hidden text (invisible through an overlay), and displays it
when prompting the user.

We lack a way to reveal truly invisible text when performing a search
and replace.  The URL of a bracket link in Org is an example of such
truly invisible text.

Juri's solution to add 'open-all could also be used in perform-replace
to let the user see truly invisible matches before replacing them.

So the *solutions* are related, if not the problems themselves.

-- 
 Bastien





  reply	other threads:[~2014-01-21 14:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 14:55 bug#16493: 24.3.50; (setq search-invisible t) is useless, let's allow to turn visible-mode temporarily on Bastien Guerry
2014-01-21  7:57 ` Juri Linkov
2014-01-21 11:15   ` Bastien
2014-01-21 11:19     ` Bastien
2014-01-21 13:54     ` Stefan Monnier
2014-01-21 14:20       ` Bastien [this message]
2014-11-05 15:30         ` Stefan Monnier
2014-11-09 19:30           ` Juri Linkov
2014-11-18 10:41             ` Bastien
2014-11-18 16:48               ` Stefan Monnier
2014-11-19  8:53                 ` Bastien
2018-04-28 14:28                   ` Bastien
2018-04-28 18:11                     ` Stefan Monnier
2018-04-29  9:50                       ` Bastien
2019-04-30  4:34                         ` Noam Postavsky
2019-04-30  5:06                           ` Eli Zaretskii
2019-04-30 11:15                             ` Noam Postavsky
2019-04-30 12:13                           ` Stefan Monnier
2019-04-30 12:24                             ` Noam Postavsky
2019-04-30 12:45                               ` Stefan Monnier
2019-04-30 15:21                                 ` Eli Zaretskii
2019-05-01 11:40                                   ` Noam Postavsky
2019-05-01 17:02                                     ` Eli Zaretskii
2019-05-01 17:29                                       ` Stefan Monnier
2019-05-11 15:27                                       ` Noam Postavsky
2019-05-11 15:50                                         ` Eli Zaretskii
2019-05-11 20:06                                           ` Stefan Monnier
2019-05-12  4:23                                             ` Eli Zaretskii
2019-05-12 15:35                                               ` Stefan Monnier
2019-05-12 15:59                                                 ` 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=87k3dtl8lp.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=16493@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).