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 18:33:13 +0300 [thread overview]
Message-ID: <86tt2ksbwm.fsf@gnu.org> (raw)
In-Reply-To: <20250806145304.GA48050@cventin.lip.ens-lyon.fr> (message from Vincent Lefevre on Wed, 6 Aug 2025 16:53:04 +0200)
> Date: Wed, 6 Aug 2025 16:53:04 +0200
> From: Vincent Lefevre <vincent@vinc17.net>
>
> This patch provides papersize information for "refcard.dvi".
> Without this, xdvi uses the default papersize configured on
> the machine to display the dvi file; this may yield truncated
> output:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=461815;filename=refcard-dvi.png;msg=15
>
> This patch fixes
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461815
>
> Other explanations are given at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461613
>
> diff --git a/gdb/doc/refcard.tex b/gdb/doc/refcard.tex
> index 8a402620bcc..9628c1d20fe 100644
> --- a/gdb/doc/refcard.tex
> +++ b/gdb/doc/refcard.tex
> @@ -100,6 +100,7 @@
> \pdfpagewidth=\totalwidth % width of paper in pdf output
> \pdfpageheight=\totalheight % height of paper in pdf output
> \fi
> +\special{papersize=11in,8.5in} % for dvi output
> %------- end papersize params
> %%
> %% change according to personal taste, not papersize dependent
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?
next prev parent reply other threads:[~2025-08-06 15:33 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 [this message]
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
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=86tt2ksbwm.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