46,7 +5246,7 @@
>
> @c -
>
> -@node Tabs and Leaders, Input Conventions, Adjustment, Text
> +@node Tabs and Leaders, Requests and Macros, Adjustment, Text
> @subsection Tabs and Leaders
>
> @cindex horizon
$ diff -u groff.texi.orig groff.texi
--- groff.texi.orig 2024-03-05 18:20:59.940460376 +
+++ groff.texi 2024-03-05 18:23:00.884303572 +
@@ -5246,7 +5246,7 @@
@c -
-@node Tabs and Leaders, Input Conventions
l
want the leaders of different TOC entries to align vertically:
.de PG
\\a\\t\\$1
.br
.di
.in
.ll
.nf
.ta \w'\\$1'u%\w'\(LC'u+\\n(.lu-\w'\\$1'u-\w'\(LC'u \\n(.luR
.XX
..
(and if you're using different fonts/sizes, making sure the
leaders are always the same width).
leade
Am 5. September 2023 23:41:36 MESZ schrieb Peter Schaffter :
>On Mon, Sep 04, 2023, Tadziu Hoffmann wrote:
>> I think leaders are meant to be used in conjunction with
>> diversions. When they are used in already formatted text,
>> all required dimensions are kn
On Mon, Sep 04, 2023, Tadziu Hoffmann wrote:
> I think leaders are meant to be used in conjunction with
> diversions. When they are used in already formatted text,
> all required dimensions are known, allowing n/troff to
> compute the number of leader character repetitions plus an
Lennart --
On Sun, Sep 03, 2023, Lennart Jablonka wrote:
> Do you now understand what’s going on, ignoring how useful or useless a
> design this is?
Your explanation was exactly what I needed to conceptualize leader
behaviour. Many thanks. I took a couple of readings, but I've got
it now.
--
> Rare? Maybe. But not so rare that a macro package need not
> be prepared for it.
I think leaders are meant to be used in conjunction with
diversions. When they are used in already formatted text,
all required dimensions are known, allowing n/troff to
compute the number of leader cha
At 2023-09-03T23:43:29+, Lennart Jablonka wrote:
> What I intended to express is an explanation for how it could come to
> be that tabs and leaders behave in that way: It was possible because
> quite seldom someone wanted a tab or leader in filled text. Because
> long headi
Quoth Peter Schaffter:
On Sat, Sep 02, 2023, Lennart Jablonka wrote:
The point is that the width of the line of periods is determined
by its position on the input line. That is confusing, yet it
also doesn’t usually matter: You seldom use tabs or leaders in
filled text.
Actually, no. I
haracter...behaves similarly to a tab character: it
moves to the next tab stop. The difference is that for this
movement, the default fill character is a period '.'."
move to the tab stop at the right margin and fill the space with
leaders, no? I can see where there might be problems in si
ence is that for this
movement, the default fill character is a period '.'."
move to the tab stop at the right margin and fill the space with
leaders, no? I can see where there might be problems in situations
similar what the docs have to say about \R, but here I don't think
that's th
On Sat, Sep 02, 2023, Lennart Jablonka wrote:
> The point is that the width of the line of periods is determined
> by its position on the input line. That is confusing, yet it
> also doesn’t usually matter: You seldom use tabs or leaders in
> filled text.
Actually, no. I discovere
osted here in a while suggested that we don't need names for
modes like that, even (or especially?) when they're the default.
That is confusing, yet it also doesn’t usually matter: You seldom use
tabs or leaders in filled text.
Even if that is the case, we should explicitly specify the behavior, an
so doesn’t usually matter: You seldom use
> tabs or leaders in filled text.
Even if that is the case, we should explicitly specify the behavior, and
document it in a way that is comprehensible to users.
I challenge you to explain the following.
$ cat EXPERIMENTS/long-leader2.roff
.ds ld \a\&quo
That is confusing, yet it also doesn’t usually matter:
You seldom use tabs or leaders in filled text.
[self-follow-up]
Hi Peter,
On second thought--in the form of empirical measurements rather than
hand-waving conjecture--I think you've found a bug.
Consider the following input, which I've degraded to an ASCII spelling
of "chateau" to permit some comparative analysis (keep reading).
$ cat
would suggest?
Yes. This has been documented for a long time, but I don't think very
clearly. Until (he boasted) groff 1.23.0.
===snip===
5.12.1 Leaders
--
Sometimes it is desirable to fill a tab stop with a given glyph, but
also use tab stops normally on the same output line. An e
I'm having trouble making sense of leader behaviour.
cat < The château into which my valet had ventured to make forcible en‐
trance, rather than permit me, in my deparately wounded condi‐
tion, to pass a night in the open air
Notice that \a is not interpolating leaders. Replac
URL:
<https://savannah.gnu.org/bugs/?64239>
Summary: [eqn] handle input leaders like input tabs
Group: GNU roff
Submitter: gbranden
Submitted: Tue 23 May 2023 08:09:18 AM UTC
Category: Preprocess
gbranden pushed a commit to branch master
in repository groff.
commit ca9b3276792c073964112f3c96e65ae0192318b5
Author: G. Branden Robinson
AuthorDate: Mon Aug 29 17:28:42 2022 -0500
[docs]: Revise discussion of tabs and leaders.
* doc/groff.texi (Tab Stops): Rename subsection/node
Update of bug #61157 (project groff):
Status: In Progress => Fixed
Open/Closed:Open => Closed
___
Follow-up Comment #8:
I got the
gbranden pushed a commit to branch master
in repository groff.
commit ce4ec3b65efbae2af0cd21b255bd09814a1e2085
Author: G. Branden Robinson
AuthorDate: Wed May 18 02:42:36 2022 -0500
doc/groff.texi: Revise material on tabs, leaders.
* Speak of ISO encodings, not "ASCII".
gbranden pushed a commit to branch master
in repository groff.
commit 3439bd41966d8c4d970f3ce777279f298a5f9504
Author: G. Branden Robinson
AuthorDate: Wed Jan 19 19:53:17 2022 +1100
[ms]: Don't add leaders that don't lead anywhere.
* tmac/s.tmac (toc*end-entry): If no page number
Update of bug #61157 (project groff):
Assigned to: keithmarshall => gbranden
Planned Release:None => 1.23.0
___
Follow-up Comment #7:
Hi Branden,
Update of bug #61157 (project groff):
Status:None => In Progress
Assigned to:None => keithmarshall
___
Follow-up Comment #6:
Hi, Keith!
[comment
Follow-up Comment #5, bug #61157 (project groff):
Branden,
[comment #4 comment #4:]
> [comment #3 comment #3:]
> > [comment #1 comment #1:]
> > > Will you follow up with a patch to the documentation, or would [you]
prefer me to write it?
> > I'll tackle the manpage update, if you wish, ...
>
Follow-up Comment #4, bug #61157 (project groff):
[comment #3 comment #3:]
> [comment #1 comment #1:]
> > Will you follow up with a patch to the documentation, or would [you]
prefer me to write it?
> I'll tackle the manpage update, if you wish, ...
Proposed manpage patch attached.
(file #51924)
Follow-up Comment #3, bug #61157 (project groff):
[comment #1 comment #1:]
> This proposal seems fine to me.
Thanks, Branden.
> Will you follow up with a patch to the documentation, or would prefer me to
write it?
I'll tackle the manpage update, if you wish, but I am not at all familiar with
Follow-up Comment #2, bug #61157 (project groff):
[comment #1 comment #1:]
> ... I intended to document FS-MARK but found myself confused with respect to
use cases. I'll follow up with you about that elsewhere since it's off-topic
for this ticket.
There is a strong hint to the use-case, on
Follow-up Comment #1, bug #61157 (project groff):
This proposal seems fine to me. Will you follow up with a patch to the
documentation, or would prefer me to write it?
Also, I intended to document FS-MARK but found myself confused with respect to
use cases. I'll follow up with you about that
URL:
<https://savannah.gnu.org/bugs/?61157>
Summary: [ms]: Add support for user-defined styling of TOC
leaders
Project: GNU troff
Submitted by: keithmarshall
Submitted on: Tue 14 Sep 2021 09:33:25 PM UTC
Category:
gbranden pushed a commit to branch master
in repository groff.
commit 11f79d67c65916a8c7db55f58f070787209e4069
Author: G. Branden Robinson
AuthorDate: Mon Nov 16 18:27:54 2020 +1100
[docs]: Revise bits on whitespace, tabs, leaders.
* doc/groff.texi:
(Input Conventions): Note
32 matches
Mail list logo