From: Eli Zaretskii <eliz@gnu.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Provide papersize for refcard.dvi
Date: Wed, 06 Aug 2025 22:02:27 +0300 [thread overview]
Message-ID: <86ikj0s27w.fsf@gnu.org> (raw)
In-Reply-To: <20250806164748.GY2576@qaa.vinc17.org> (message from Vincent Lefevre on Wed, 6 Aug 2025 18:47:48 +0200)
> Date: Wed, 6 Aug 2025 18:47:48 +0200
> From: Vincent Lefevre <vincent@vinc17.net>
> Cc: gdb-patches@sourceware.org
>
> On 2025-08-06 19:30:52 +0300, Eli Zaretskii wrote:
> > > Date: Wed, 6 Aug 2025 18:00:24 +0200
> > > From: Vincent Lefevre <vincent@vinc17.net>
> > > Cc: gdb-patches@sourceware.org
> > >
> > > On 2025-08-06 18:33:13 +0300, Eli Zaretskii wrote:
> > > > Thanks, but we need to bring some TeX and DVI expert on board. I
> > > > wonder why GDB needs this whereas, for example, Emacs doesn't. Is
> > > > there something fundamentally wrong with the GDB refcard?
> > >
> > > That's strange, because I get exactly the same issue with Emacs.
> >
> > How come? I regularly produce refcard.pdf for Emacs, and never saw
> > any such problems. Do you perhaps have some unusual default
> > definition of paper size?
>
> PDF is different from DVI.
Doesn't PDF generation go through DVI? And if it doesn't, then why
should we care about DVI nowadays?
Anyway, I feel we should take this discussion to the Texinfo list,
where we will find people who know about TeX and DVI much more than I
do, and could give some useful advice.
next prev parent reply other threads:[~2025-08-06 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 14:53 Vincent Lefevre
2025-08-06 15:33 ` Eli Zaretskii
2025-08-06 16:00 ` Vincent Lefevre
2025-08-06 16:30 ` Eli Zaretskii
2025-08-06 16:47 ` Vincent Lefevre
2025-08-06 19:02 ` Eli Zaretskii [this message]
2025-08-06 22:28 ` Vincent Lefevre
2025-08-07 5:50 ` Eli Zaretskii
2025-08-07 9:05 ` Vincent Lefevre
2025-08-07 9:55 ` Eli Zaretskii
2025-08-08 16:15 ` Eli Zaretskii
2025-08-08 17:25 ` Vincent Lefevre
2025-08-08 17:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ikj0s27w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=vincent@vinc17.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox