At 2018-04-17T00:05:59+1000, John Gardner wrote:
> I'm referring to a select choice of words that just happens to neatly fall
> against the 72-character limit... =) Here's the commit message I was
> referring to:
>
> Like man(7), mdoc(7) is a macro package for marking up computer manuals.
> The ma
Apologies for the out-of-sync response: Ingo's e-mail was binned as spam by
Gmail. Apologies if it sounded like I was ignoring you. =) (I was wondering
where Ralph drew this from:
> *The name of that standard section in man(7) and mdoc(7) is "EXIT**STATUS",
> not "Exit Status" nor "Exit status" n
At 2018-04-21T04:19:06+1000, John Gardner wrote:
> I've been so anxious to finish this and show everybody but I'm blocked on a
> retarded issue of panning/zooming transformations that require a
> math-empowered brain that's better than mine... :(
I remember some linear algebra, if that might be he
First, leave performance expectations at the door. The ambitious experiment
I describe below is intended to provide airtight handling for a conversion
medium which is inherently lossy (Roff -> HTML/SVG/CSS/et al, Markdown, and
Markdown with GitHub-flavoured options).
*1. Handling semantics*
We al
>
> *Hmm, that must be new in CSS (i stopped at CSS2).*
Do you mean attribute selectors?
these[ones-like$="this?"] { }
They've actually enjoyed universal support for quite some time now... =)
They were included in the first revision of the CSS2 specification, IIRC.
*But that has nothing to do
John Gardner wrote:
|Every instance of the "SHOUTED" headings can be uppercased too, even when
|used outside their role as a heading.
|
|The CSS to achieve this:
|
|a[href="#name"],
|a[href="#description"],
|a[href="#authors"] {
|
|text-transform: uppercase;
|}
|
|Will typecast any li
Every instance of the "SHOUTED" headings can be uppercased too, even when
used outside their role as a heading.
The CSS to achieve this:
a[href="#name"],
a[href="#description"],
a[href="#authors"] {
text-transform: uppercase;
}
Will typecast any link pointing to in majuscule "NAME".
It's all C
Ralph Corderoy wrote:
|Ingo wrote:
|> The name of that standard section in man(7) and mdoc(7) is "EXIT
|> STATUS", not "Exit Status" nor "Exit status" nor "exit status".
|
|The shouting section heading makes it easier to find that heading rather
|than the same word occurring elsewhere, e.g.
>
> Begging your pardon ... who's pdfmark macros?
>
Ahaha, my bad. I recall well the credit Deri gave in pdf.tmac:
> *Much of the code in this macro has come from the excellent original work
> by*
> *Keith Marshall (see attribution in the pdfmark.tmac file). I, however,**am
> solely responsible
Hi,
Ingo wrote:
> The name of that standard section in man(7) and mdoc(7) is "EXIT
> STATUS", not "Exit Status" nor "Exit status" nor "exit status".
The shouting section heading makes it easier to find that heading rather
than the same word occurring elsewhere, e.g. `ENVIRONMENT'.
And if the .SH'
On 20/04/18 19:19, John Gardner wrote:
> And as if that weren't enough, the renderer includes first-class
> support for Deri Jame's pdfmark macros ...
Begging your pardon ... who's pdfmark macros?
Hi John,
John Gardner wrote on Sat, Apr 21, 2018 at 06:21:33AM +1000:
> Ingo Schwarze wrote:
>> and blanks in fragment names replaced by underscores rather than
>> hyphens, for example:
> The underscores look really jarring...
> what's the argument against using dashes instead?
$ man -k Sh,S
>
>
>
> *Unless you have strong reasons for the different syntax, pleaseconsider
> using the syntax established in the new man.cgi(8) a fewyears ago: *
> * protocol://[manpath/][arch/]name[.sec][#fragment]*
Thank you for bringing this to me. =) Yes I most certainly will use this
syntax (didn't
On 2/15/18, Bertrand Garrigues wrote:
> If you think there are some important fixes that
> must be passed (I haven't reviewed the Savannah bug list for a while,
> I'll check in the next days) please feel free to comment on this list.
I wouldn't consider this an *important* fix, but bug #42191 doe
Hi John,
John Gardner wrote on Sat, Apr 21, 2018 at 04:19:06AM +1000:
> My Troff previewer will be doing just that for
> man://mandoc/1/. =)
> Will probably add support for subsection-linking with fragment
> identifiers too:
> man://mandoc/1/#exit-status
Unless you have strong reasons for the di
>
>
> *This is the thing I miss most about Konqueror: you could type a URI
> like**“man:mdoc”
> and it would format and display the page*
There'll be a feature like that in Atom. The editor recently introduced a
feature where extension authors can register an external/custom protocol to
open lin
Ingo Schwarze wrote:
> So yeah, even though proportional font is slowly becoming more
> widely used, you may be right: The legacy of Wolfram Schneider's
> FreeBSD man.cgi is still pretty widespread and even motivated Michael
> Stapelberg to use a fixed width font for Debian, even though the
> r
John Gardner wrote:
> It's easier than you think.You just have to separate presentational
> semantics from structural and content-related ones.
I’m fond of saying ‘All you have to do is…’ is one of the biggest lies ever
told. ;-D
> I've seen grohtml's complexity and was bewildered. Hence why
On Thu, Apr 19, 2018 at 06:48:19PM +0200, Ingo Schwarze wrote:
> Colin Watson wrote on Thu, Apr 19, 2018 at 10:06:28AM +0100:
> > "man ./apropos.1", as Nate pointed out. man-db's heuristic is that if
> > the page name contains a slash then it's surely a path name instead and
> > should be treated
19 matches
Mail list logo
