unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 72241@debbugs.gnu.org
Subject: bug#72241: 31.0.50; [PATCH] Use a dedicated buffer for `doc-view-open-text'
Date: Tue, 23 Jul 2024 09:55:14 +0200	[thread overview]
Message-ID: <87ed7kk0f1.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <87v80xwb3d.fsf@gnu.org> (Tassilo Horn's message of "Mon, 22 Jul 2024 20:11:34 +0200")

Tassilo Horn <tsdh@gnu.org> writes:

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
> Hi Manuel,
>
>> Here is a patch for DocView that makes it use a dedicated buffer for
>> the text representation of a document.  This is what was suggested by
>> Stefan M. in a comment (circa 2019).
>
> I think that's a good idea in general and addresses a FIXME.
>
> Since it doesn't fix a bug, I think it should only be applied to
> master.

Yes, I also do think so.

> Oh, and in the commit message there's an "an" where an "and" was meant.
> And maybe a "text-contents buffer" is a slightly better term than "doc's
> contents buffer".

Ok.  I'll fix that.

[...]

> (info "(emacs) Document View") might need a small update for the
> description where some requirement is not met (e.g., emacs in a TTY
> frame) where it says that "the (document) buffer" is put in text mode
> when one answers the query if the contents should be shown as plain text
> with yes.

I have not tested in a TTY… maybe I should 😅
-- 
Manuel Giraud





      parent reply	other threads:[~2024-07-23  7:55 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
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 [this message]

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=87ed7kk0f1.fsf@ledu-giraud.fr \
    --to=bug-gnu-emacs@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).