From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 72241@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#72241: 31.0.50; [PATCH] Use a dedicated buffer for `doc-view-open-text'
Date: Mon, 22 Jul 2024 21:48:27 +0300 [thread overview]
Message-ID: <86jzhd9sas.fsf@gnu.org> (raw)
In-Reply-To: <87r0blw9s5.fsf@gnu.org> (message from Tassilo Horn on Mon, 22 Jul 2024 20:39:54 +0200)
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: 72241@debbugs.gnu.org, manuel@ledu-giraud.fr
> Date: Mon, 22 Jul 2024 20:39:54 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can you tell in what way the behavior will change after this? I'd
> > like to think whether a NEWS entry is necessary and what to day there.
>
> Right now, when you open foo.pdf you see the images generated from the
> PDF. When you do C-c C-t, it'll replace the foo.pdf buffer contents
> with the plain text contents of the PDF. With another C-c C-c, the
> contents are again replaced with the PDF and you see the images again.
>
> With Manuel's patch, C-c C-t shows the plain text contents in a separate
> buffer foo.pdf/text. C-c C-c in there kills that separate buffer and
> switches back to the original foo.pdf buffer.
>
> So basically everything you have to do stays the same but there are now
> two instead of just one buffer. That has the advantage that you can
> switch between them and removes the possibility that you accidentally
> overwrite your PDF with the plain text contents (which in what Stefan's
> FIXME was about).
Thanks, I think this is enough in users' faces to warrant a NEWS
entry.
next prev parent reply other threads:[~2024-07-22 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 8:26 bug#72241: 31.0.50; [PATCH] Use a dedicated buffer for `doc-view-open-text' Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-22 18:11 ` Tassilo Horn
2024-07-22 18:29 ` Eli Zaretskii
2024-07-22 18:39 ` Tassilo Horn
2024-07-22 18:48 ` Eli Zaretskii [this message]
2024-07-23 8:10 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 10:39 ` Tassilo Horn
2024-07-23 12:00 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 12:16 ` Tassilo Horn
2024-07-23 13:45 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 14:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 6:25 ` Tassilo Horn
2024-07-23 7:55 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86jzhd9sas.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72241@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=tsdh@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 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).