Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Fri, 08 Aug 2025 20:48:38 +0300	[thread overview]
Message-ID: <86qzxln1qh.fsf@gnu.org> (raw)
In-Reply-To: <20250808172503.GH2576@qaa.vinc17.org> (message from Vincent Lefevre on Fri, 8 Aug 2025 19:25:03 +0200)

> Date: Fri, 8 Aug 2025 19:25:03 +0200
> From: Vincent Lefevre <vincent@vinc17.net>
> Cc: gdb-patches@sourceware.org
> 
> On 2025-08-08 19:15:07 +0300, Eli Zaretskii wrote:
> > > Date: Thu, 07 Aug 2025 12:55:20 +0300
> > > From: Eli Zaretskii <eliz@gnu.org>
> > > Cc: gdb-patches@sourceware.org
> > > 
> > > > Date: Thu, 7 Aug 2025 11:05:24 +0200
> > > > From: Vincent Lefevre <vincent@vinc17.net>
> > > > Cc: gdb-patches@sourceware.org
> > > > 
> > > > On 2025-08-07 08:50:14 +0300, Eli Zaretskii wrote:
> > > > > That's true, but there are TeX experts there.  If you know of a better
> > > > > place, we could discuss this there.  I unfortunately don't know enough
> > > > > about this to make a decision about the right solution.
> > > > 
> > > > FYI, the TeX Users Group has mailing-lists:
> > > > 
> > > >   https://tug.org/mailman/listinfo
> > > > 
> > > > texhax seems to be the one for general TeX questions.
> > > 
> > > Thanks, posted a question there.
> > 
> > Given the responses there, can you post (and hopefully test) an
> > improved patch?
> 
> Note: my old patch was based on what was done in PARI.
> 
> I've attached a new patch. It still uses \ifx\pdfoutput\undefined
> because the suggested \ifnum\pdfoutput<1 gives an error.

Shouldn't this error be discussed with the TeX gurus that recommended
it, before we roll out our own solution?

      reply	other threads:[~2025-08-08 17:49 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86qzxln1qh.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