At 2020-12-16T20:30:33-0600, Dave Kemper wrote:
> On 12/15/20, Dorai Sitaram wrote:
> > Thanks Dave, for the suggestion. That doesn't seem to be the
> > problem, however, on my machine (Ubuntu 20.10). No-argument cat
> > works as expected.
>
> Then something peculiar to the Ubuntu groff seems
At 2020-12-16T10:54:40+, Colin Watson wrote:
> On Wed, Dec 16, 2020 at 11:35:12AM +1100, G. Branden Robinson wrote:
> > What do people think about a GROFF_USE_UTC environment variable that
> > causes troff to call gmtime() instead of localtime()?
>
> How would this differ from just setting TZ=
Groff mailing list,
A (second) question about "mom" and over-striking of text.
I started with the "mom" example file named "sample_docs.mom" and (only) added
the Unicode "\[u2026]" for the ellipsis character in the middle of line 482.
In the resulting PDF output file, the ellipsis appears on pag
On Sat, 19 Dec 2020, Karthik Suresh wrote:
First, when you do the purely mechanical operations of typing, type
so subsequent editing will be easy. Start each sentence on a new line.
Make lines short, and break lines at natural places, such as after
commas and semicolons, rather than randoml
On 19/12/2020 22:36, James K. Lowden wrote:
On Sat, 19 Dec 2020 20:18:19 +
Karthik Suresh wrote:
I think it's also the advice Brian Kernighan gives about breaking
at natural phrase points in the text as we tend to edit a phrase at a
time.
I hadn't heard that. Do you know where you re
On Sat, 19 Dec 2020 20:18:19 +
Karthik Suresh wrote:
> I think it's also the advice Brian Kernighan gives about breaking
> at natural phrase points in the text as we tend to edit a phrase at a
> time.
I hadn't heard that. Do you know where you read it?
A had a college professor who claim
On 12/19/20, Peter Schaffter wrote:
> On Sat, Dec 19, 2020, Ulrich Lauther wrote:
>> In my opinion it is good style to start every sentence on a new
>> source line.
>
> A piece of advice I have been happily ignoring since sometime back
> in the 90s.
...
> This is the the first paragraph of _Bleak
On 12/19/20, Dorai Sitaram wrote:
> groff pretty much forces one to use two spaces after sentence-ending
> punctuation, unless it's at the end of a source line. Is there a way to
> avoid this, so that the space is uniform regardless of whether the ending
> punctuation occurs mid- or end-line?
Usi
In my opinion it is good style to start every sentence on a new
source line.
A piece of advice I have been happily ignoring since sometime back
in the 90s. Certain kinds of texts (scientific, technical) and the
ways they are to be used (e.g. one off, or formatted for multiple media
types an
I've been using a simple solution successfully for years.
In my own macros I wrote and use, I include the troff/groff provision
for specifying the end-of-sentence ratio
as follows: " .ss 12 20"
End-of-sentence identified by two space characters creates a space equal
to normal space times 1.
Ha! Glad I'm not the only one who is driven up the wall by newlines at the end
of every sentence. I've heard this policy touted so many times by folk who are
obviously expert (even those who don't troff), and I have no doubt at all it
works for them.
I just can't read or edit it to save my l
On Sat, Dec 19, 2020, Ulrich Lauther wrote:
> On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> > groff pretty much forces one to use two spaces after
> > sentence-ending punctuation, unless it's at the end of a source
> > line.
>
> In my opinion it is good style to start every sent
Peter,
Thanks very much.
I processed the same document with the 2.4-4_c macro version (as opposed to
2.1-c_1) and confirm the correct behavior where the column text now appears as
expected, with no overstriking.
Thanks again.
-- Steve Ross
On Friday, December 18, 2020, 10:02:36 PM CST, Pet
Maybe you can look at the . ss request
Which sets interword spacing as first argument and the second argument as
sentence space
Kind regards
Wim Stockman
Op za 19 dec. 2020 13:36 schreef Oliver Corff :
> Hi Dorai,
>
> the point behind the end-of-source-line rule is simple, and is hidden in
> man
Hi Dorai,
the point behind the end-of-source-line rule is simple, and is hidden in
many introductory chapters of textbooks on troff and groff: You are not
forced (and even less encouraged) to preempt any formatting in your
input text. None of your efforts with regard to line length, intended
line
On Sat, 19 Dec 2020, Ulrich Lauther wrote:
On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
groff pretty much forces one to use two spaces after sentence-ending
punctuation, unless it's at the end of a source line.
In my opinion it is good style to start every sentence on a n
On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> groff pretty much forces one to use two spaces after sentence-ending
> punctuation, unless it's at the end of a source line.
In my opinion it is good style to start every sentence on a new source line.
This is helpful for editing t
groff pretty much forces one to use two spaces after sentence-ending
punctuation, unless it's at the end of a source line. Is there a way to avoid
this, so that the space is uniform regardless of whether the ending punctuation
occurs mid- or end-line? (I could resign myself to always type 2 spa
18 matches
Mail list logo
