> Since you have a real use case here, and the case of someone trying
> to use a degree sign without the EC font is only hypothetical, I
> have instated your proposed definition for \textdegree.
Thanks.
> I found that copying and pasting produced an extra space before the
> degree sign, like 45
On Sat, Nov 12, 2022 at 11:25:04PM +, Gavin Smith wrote:
> > I can do that change/commit on the 7.0 branch.
>
> OK that's fine. You can either do
>
> git cherry-pick b238da561dad6
>
> and then to remove parts of the commit, do
>
> git reset --soft HEAD^
>
> followed by
>
> git reset .
>
On Sun, Nov 13, 2022 at 12:15:19AM +0100, Patrice Dumas wrote:
> On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
> > While other changes since the last release may be valuable, I don't see
> > that they are urgent. Please discuss it if there's anything vital that
> > people think that
On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
> While other changes since the last release may be valuable, I don't see
> that they are urgent. Please discuss it if there's anything vital that
> people think that should be included.
>
I think that the following change should be in
On Sat, Nov 12, 2022 at 2:56 PM Gavin Smith
wrote:
> On Sat, Nov 12, 2022 at 02:30:11PM -0800, Raymond Toy wrote:
> > On Sat, Nov 12, 2022 at 2:27 PM Gavin Smith
> > wrote:
> >
> > > On Tue, Nov 08, 2022 at 07:55:44PM +, Gavin Smith wrote:
> > > > > No, you just cut a new release branch. Th
On Sat, Nov 12, 2022 at 11:53:19PM +0100, Patrice Dumas wrote:
> On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
> >
> > Commit 15ef3457ed1 (on release branch)
> >
> > This led to test result changes in
> > tp/t/results/sectioning/unnumbered_before_top_node.pl
> > tp/t/results/prefor
On Sat, Nov 12, 2022 at 11:53:19PM +0100, Patrice Dumas wrote:
> It looks like a bug,
> @@ -9916,6 +9927,7 @@ sub output($$)
>if (!$fulltitle and $self->{'global_commands'}->{'titlefont'}
>and $self->{'global_commands'}->{'titlefont'}->[0]->{'args'}
>and
> defined($self->{'glo
On Sat, Nov 12, 2022 at 02:30:11PM -0800, Raymond Toy wrote:
> On Sat, Nov 12, 2022 at 2:27 PM Gavin Smith
> wrote:
>
> > On Tue, Nov 08, 2022 at 07:55:44PM +, Gavin Smith wrote:
> > > > No, you just cut a new release branch. The release branch is only for
> > > > a certain release or a seri
On Sat, Nov 12, 2022 at 10:18:31PM +, Werner LEMBERG wrote:
> LilyPond's input encoding is UTF-8; markup strings must be thus
> emitted as UTF-8, too. Its Texinfo documentation extracts code
> snippets from master files (using the `lilypond-book` script),
> compiles them for graphical output,
On Sat, Nov 12, 2022 at 10:26:54PM +, Gavin Smith wrote:
>
> Commit 15ef3457ed1 (on release branch)
>
> This led to test result changes in
> tp/t/results/sectioning/unnumbered_before_top_node.pl
> tp/t/results/preformatted/titlefont_in_example.pl
>
> which weren't on the master branch - in b
On Sat, Nov 12, 2022 at 2:27 PM Gavin Smith
wrote:
> On Tue, Nov 08, 2022 at 07:55:44PM +, Gavin Smith wrote:
> > > No, you just cut a new release branch. The release branch is only for
> > > a certain release or a series of releases, depending on the
> > > development strategy. Basically,
On Tue, Nov 08, 2022 at 07:55:44PM +, Gavin Smith wrote:
> > No, you just cut a new release branch. The release branch is only for
> > a certain release or a series of releases, depending on the
> > development strategy. Basically, as long as you expect the next
> > release to be a bugfix rel
> The work for me.
D'oh, should have been "This works for me."
Werner
>> Well, for cut and paste, `\circ` is *not* an alternative, since it
>> maps to U+25E6 (WHITE BULLET) in font `cmsy10.pfb`. This might not
>> be an issue in math, but for code listings typeset with typewriter
>> it would be really nice to get it right.
>
> Can you give us an idea of when or why
> I've often wanted to try to build the Lilypond Texinfo docs to see
> how well they work, but I haven't been able to find easily
> downloadable sources on the Lilypond website. Is there somewhere
> that such sources would be available, or would I need to compile
> Lilypond completely from sourc
On Tue, Nov 08, 2022 at 11:30:30AM +, Werner LEMBERG wrote:
> * Unpack the attached tarball and execute
I've often wanted to try to build the Lilypond Texinfo docs to see
how well they work, but I haven't been able to find easily
downloadable sources on the Lilypond website. Is there somewher
On Sat, Nov 12, 2022 at 02:42:34PM +, Werner LEMBERG wrote:
> Well, for cut and paste, `\circ` is *not* an alternative, since it
> maps to U+25E6 (WHITE BULLET) in font `cmsy10.pfb`. This might not be
> an issue in math, but for code listings typeset with typewriter it
> would be really nice t
On Sat, Nov 12, 2022 at 12:26:28PM +0100, Vincent Lefevre wrote:
> On 2022-11-12 10:23:13 +, Gavin Smith wrote:
> > On Wed, Nov 09, 2022 at 04:44:07PM +0100, Vincent Lefevre wrote:
> > > It seems that Texinfo adds something like {} at the beginning of
> > > the Texinfo macro expansion
> >
> >
>> [...] I think a better solution is below, which retains U+00B0 for
>> copy and paste.
>
> This uses the European Computer Modern fonts, which normally we have
> only used when necessary. Hence, this would have a chance (probably
> small) of breaking for a document with a degree sign on a sys
On Sat, Nov 12, 2022 at 12:40:11PM +0100, Vincent Lefevre wrote:
>
> But "down" is the reverse of "up". So, if you know all the "up"
> relations, you can deduce all the "down" relations, i.e. all the
> children. Then the issue is to sort the children, but I suppose
> that this could be done by loo
> Date: Sat, 12 Nov 2022 13:28:17 +0100
> From: Vincent Lefevre
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org, 989...@bugs.debian.org
>
> > > But "down" is the reverse of "up".
> >
> > No, it isn't. It is only the reverse of "up" if the node structure is
> > a perfect tree.
>
> But if th
On Wed, Aug 24, 2022 at 08:36:50PM +0200, Patrice Dumas wrote:
> > My preference would be to leave the code as it is now, as it looks fairly
> > complicatedm and it is one more thing to break when the code gets a
> > wider audience after a new release, on top of other unexpected breakages,
> > whic
On 2022-11-12 14:00:25 +0200, Eli Zaretskii wrote:
> > Date: Sat, 12 Nov 2022 12:40:11 +0100
> > From: Vincent Lefevre
> >
> > But "down" is the reverse of "up".
>
> No, it isn't. It is only the reverse of "up" if the node structure is
> a perfect tree.
But if the node structure is not a perfe
On Sat, Nov 12, 2022 at 12:40:11PM +0100, Vincent Lefevre wrote:
> But "down" is the reverse of "up". So, if you know all the "up"
> relations, you can deduce all the "down" relations, i.e. all the
> children. Then the issue is to sort the children, but I suppose
> that this could be done by lookin
> Date: Sat, 12 Nov 2022 12:40:11 +0100
> From: Vincent Lefevre
>
> > > Oops, I misread the file. I actually think that it is correct.
> > > IMHO, to get the tree structure, you should not follow the menu,
> > > but only the "File:" lines.
> >
> > You can't: SPC and DEL are supposed to traverse
On 2022-11-12 13:27:59 +0200, Eli Zaretskii wrote:
> Because they don't say enough, not when a node has sub-nodes.
> Backspace in a node A that has sub-nodes should go to the sub-node of
> A which is the _last_ one in the menu in the node A, exactly like SPC
> in such a node should go to the _first
On Sat, Nov 12, 2022 at 12:26:28PM +0100, Vincent Lefevre wrote:
> The first comment in
>
> https://tex.stackexchange.com/a/1932/58921
>
> says "\begingroup...\endgroup also behaves differently in math mode,
> in which {...} or \bgroup...\egroup create a subformulae with
> different spacing. A
On 2022-11-12 13:30:51 +0200, Eli Zaretskii wrote:
> > Date: Sat, 12 Nov 2022 11:56:47 +0100
> > From: Vincent Lefevre
> >
> > Oops, I misread the file. I actually think that it is correct.
> > IMHO, to get the tree structure, you should not follow the menu,
> > but only the "File:" lines.
>
> Y
> Date: Sat, 12 Nov 2022 11:56:47 +0100
> From: Vincent Lefevre
>
> Oops, I misread the file. I actually think that it is correct.
> IMHO, to get the tree structure, you should not follow the menu,
> but only the "File:" lines.
You can't: SPC and DEL are supposed to traverse the tree, not just t
On Sat, Nov 12, 2022 at 11:56:47AM +0100, Vincent Lefevre wrote:
> On 2022-11-12 11:39:41 +0100, Vincent Lefevre wrote:
> > You mean that the menus can affect the structure of the document?
> > This seems a bad and unnecessary idea. Why not just considering
> > the "File:" lines of the info manual
> Date: Sat, 12 Nov 2022 11:39:41 +0100
> From: Vincent Lefevre
> Cc: bug-texinfo@gnu.org, 989...@bugs.debian.org
>
> > * Menu:
> >
> > * Bugs::
> >
> > See that "Bugs" at the end? This is the problem: since "Bugs" is a
> > top-level node, its presence in a level-1 node's menu makes the no
On 2022-11-12 10:23:13 +, Gavin Smith wrote:
> On Wed, Nov 09, 2022 at 04:44:07PM +0100, Vincent Lefevre wrote:
> > It seems that Texinfo adds something like {} at the beginning of
> > the Texinfo macro expansion
>
> Yes, this appears to be the case. I expect it is the \bgroup and \egroup
> u
On Sat, Nov 12, 2022 at 12:12:05PM +0100, Vincent Lefevre wrote:
> On 2022-11-12 09:57:49 +, Gavin Smith wrote:
> > I've added the following to the manual:
> >
> >• Expanding macros in a math context may lead to poor spacing in TeX
> > output. For example:
> >
> > @iftex
>
On 2022-11-12 09:57:49 +, Gavin Smith wrote:
> I've added the following to the manual:
>
>• Expanding macros in a math context may lead to poor spacing in TeX
> output. For example:
>
> @iftex
> @macro atan
> \\mathop{\\rm atan}
> @end macro
>
On 2022-11-12 11:39:41 +0100, Vincent Lefevre wrote:
> You mean that the menus can affect the structure of the document?
> This seems a bad and unnecessary idea. Why not just considering
> the "File:" lines of the info manual to deduce the structure of
> the document?
>
> Actually the issue is pro
On Sat, Nov 12, 2022 at 05:45:22AM +, Werner LEMBERG wrote:
>
> > A fixed width degree sign can be got with a little difficulty. It's
> > only worth doing this if somebody is actually using degree signs in
> > a fixed width context - I don't have much interest in fixing this
> > for all of th
On 2022-11-12 09:27:34 +0200, Eli Zaretskii wrote:
> Instead of "Bugs", go to "Graphical_User_Interfaces" from the
> top-level menu. You will see this:
>
> 4 Graphical User Interfaces
> ***
>
> Several graphical user interfaces have been written for `gnuplot` and
>
On Wed, Nov 09, 2022 at 04:44:07PM +0100, Vincent Lefevre wrote:
> It seems that Texinfo adds something like {} at the beginning of
> the Texinfo macro expansion
Yes, this appears to be the case. I expect it is the \bgroup and \egroup
used in \defmacro, in this code:
\or % 1
\expandafter\x
On Wed, Nov 09, 2022 at 12:47:38PM +0100, Patrice Dumas wrote:
> I am not sure that this can be easily fixed, there are lots of caveats
> put forward in the manual because macros in TeX is an area where things
> seems to be difficult to get right, but I agree that this is an issue as
> I can't see
> Date: Sat, 12 Nov 2022 10:26:39 +0100
> From: Patrice Dumas
> Cc: Vincent Lefevre , bug-texinfo@gnu.org,
> 989...@bugs.debian.org
>
> On Sat, Nov 12, 2022 at 09:27:34AM +0200, Eli Zaretskii wrote:
> > See that "Bugs" at the end? This is the problem: since "Bugs" is a
> > top-level node,
On Sat, Nov 12, 2022 at 09:27:34AM +0200, Eli Zaretskii wrote:
> See that "Bugs" at the end? This is the problem: since "Bugs" is a
> top-level node, its presence in a level-1 node's menu makes the node
> tree not really a tree, so Backspace loops.
>
> Thus, the problem is in the way Gnuplot prod
41 matches
Mail list logo
