Hello all,
I've run into a fairly annoying bug in the mom macro package: if I let a
blockquote run across multiple pages, it will be indented only on the
first page.
Like this:
Here begins my blockquote, with normal indentation.
But here comes a page break:
-
Hello alls,
"G. Branden Robinson" wrote:
> +.ie \\$1 .tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ
> +.el .tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz
The problem with this, is that it ignores all but english languages.
"élément", for instance, would become "éLéMENT"
Hi Branden,
G. Branden Robinson wrote on Sun, Dec 16, 2018 at 04:31:01PM -0500:
> Recent discussion revealed that Ingo and I agree that less(1) is pretty
> much part of the man page experience on terminals, so it's a bit bizarre
> that the program doesn't support this as well as it should.
>
> Y
At 2018-12-16T22:51:29+0100, Tadziu Hoffmann wrote:
>
> > You have to know ahead of time that you want a
> > case-insensitive search and call less with the "-i" flag.
>
> Just press the keys "minus" and "i" in sequence to toggle
> case-(in)sensitivity while in less.
Well, I'll be damned! And on
> Just press the keys "minus" and "i" in sequence to toggle
> case-(in)sensitivity while in less.
The more(1) you know. ;-)
On Mon, 17 Dec 2018 at 08:52, Tadziu Hoffmann
wrote:
>
> > You have to know ahead of time that you want a
> > case-insensitive search and call less with the "-i" flag.
>
> You have to know ahead of time that you want a
> case-insensitive search and call less with the "-i" flag.
Just press the keys "minus" and "i" in sequence to toggle
case-(in)sensitivity while in less.
At 2018-12-17T08:21:40+1100, John Gardner wrote:
> *> How does the importance of that compare to the trouble caused for screen
> readers etc.?*
>
> Heh. It doesn't. =) Put simply, if you're searching for human text in
> prose, you'll almost always want a case-insensitive search.
Recent discussion
Hi Branden,
G. Branden Robinson wrote on Sun, Dec 16, 2018 at 01:33:43PM -0500:
> At 2018-12-16T17:15:47+0100, Ingo Schwarze wrote:
>> So i don't regard it as a big mystery how the rule "put all caps
>> into the source code for section headers" came to be. The question
>> only is whether it is w
> > making it easier for the author to spot sections when
> > skimming a file. Doubt there was any syntax highlighting
> > back then... =)
> Syntax highlighting six years before the invention of vi(1)?
> That's indeed a funny idea!
People were really creative at the time in making maximum
use
*> I've become quite spoiled by Vim's \c flag to the pattern-matcher:*
Doesn't Vi have (deliberately?) similar keybindings to Less? Or is the \c
merely a Vim thing?
I use Emacs and Atom (depending on which computer I'm on, OpenBSD or
macOS). The former has `C-s` bound to I-search, which not only
*> How does the importance of that compare to the trouble caused for screen
readers etc.?*
Heh. It doesn't. =) Put simply, if you're searching for human text in
prose, you'll almost always want a case-insensitive search.
Amusing sidenote: A screen-reader would read ".Sh" as "Ssssh...", which
woul
Hi John,
John Gardner wrote on Mon, Dec 17, 2018 at 07:25:00AM +1100:
> Tadziu Hoffmann wrote:
>> or perhaps it was considered but consciously rejected because
>> situations existed where it would be detrimental?
> It could have been to make sections more conspicuous in text editors,
Certainly
> or perhaps it was considered but consciously rejected because
> situations existed where it would be detrimental?
It could have been to make sections more conspicuous in text editors,
making it easier for the author to spot sections when skimming a file.
Doubt there was any syntax highlighting b
Hi Tadziu,
Tadziu Hoffmann wrote on Sun, Dec 16, 2018 at 07:08:06PM +0100:
> Ingo Schwarze wrote:
>> Jerry Saltzer's RUNOFF (1964) did not have a .tr request, [...]
>> By AT&T Version 3 UNIX (1973), nroff(1) did have it, [...]
> Doug McIlroy's GECOS runoff had it
Interesting.
Oh yes, now that y
> I am writing a text using the ms macros with the CB font.
> Set it at .fp 1 CB and for the text itself and the TOC it works,
> *but* for the chapter numbering.
The ms macros call ".ft B" inside the section header macro,
so it might work if you map the font "B" to "CB" with
.fp 1 B CB
inste
At 2018-12-16T17:15:47+0100, Ingo Schwarze wrote:
> So i don't regard it as a big mystery how the rule "put all caps
> into the source code for section headers" came to be. The question
> only is whether it is worth editing thousands of manual pages for
> each operating system to get rid of the ru
*> IIUC, you are working on a JavaScript program in the context> of some
gigantic heavy-weight framework to render manual pages in> real time on a
canvas while an author is editing them. Corrrect> me if i got that
wrong...*
That "heavyweight framework" is simply the World Wide Web. There is (and
> Jerry Saltzer's RUNOFF (1964) did not have a .tr request, [...]
> By AT&T Version 3 UNIX (1973), nroff(1) did have it, [...]
Doug McIlroy's GECOS runoff had it (the memo from 1969
even mentions its utility in creating unpaddable spaces),
so I assumed (perhaps wrongly) that this feature had als
Hi John,
John Gardner wrote on Mon, Dec 17, 2018 at 02:33:25AM +1100:
> I really do wish Mandoc would support the Troff intermediate
> output format.
I just had a brief look again at your message "Formal AST output
in mandoc" from January 16, and the ensuing thread, to refresh my
memory. IIUC,
Hi Tadziu,
Tadziu Hoffmann wrote on Sun, Dec 16, 2018 at 03:13:21PM +0100:
> someone wrote:
>> "LOUD, SHOUTING HEADINGS" are ultimately a relic from
>> the (tele)typewriter era.
> It's just a technical limitation of teletypes that they
> usually could not deal with different font sizes. For the
> *pages 11 to 13 are about implementing a new output format,*
I really do wish Mandoc would support the Troff intermediate output format.
Even if processing text piped between programs isn't nearly as efficient as
reading it from a compiled program, it's so much more flexible.
On Mon, 17 Dec 201
Hi Larry,
Larry Kollar wrote on Sun, Dec 16, 2018 at 02:20:32AM -0500:
> Rant the Third: How *DO* you Embed Manpages?
one very clean option is to write a mandoc output formatter.
Admittedly, that requires a one-time investment of about a week of
work for a new output format, and better coordina
> "LOUD, SHOUTING HEADINGS" are ultimately a relic from
> the (tele)typewriter era.
It's just a technical limitation of teletypes that they
usually could not deal with different font sizes. For the
actual printed manuals, the man macros traditionally had
the section headings printed one point s
Hi Erich,
> I am writing a text using the ms macros with the CB font.
> Set it at .fp 1 CB and for the text itself and the TOC it works,
> *but* for the chapter numbering.
>
> Thus, this code:
>
> .NH
> title...
> .XS
> toc-title
> .XE
>
> produces everything in CB font, except the title numbering
24 matches
Mail list logo
