Re: warning on mid-input line sentence endings
Hi Branden and Dave, > The devilish problem is that I don't know what to put > _before_ the period in the register name for _this_ > issue. > I'd like to hear suggestions. Adding on my suggestion as an innocent bystander. The style problem as I understand it is “there are multiple sentences per line” (rather than delegating one line per sentence). So how about something like “multisentenceline”, as in multiple sentences per line? It feels more natural to think about it this way rather than in terms of sentence endings. Hope that helps you brainstorm! Josh --
Re: "Writing my PhD using groff"
On Sunday, July 24, 2022, Larry McVoy wrote: > > Am I the only person who thinks that have *roff documentation in a > different > markup is crazy? > > I wrote a couple source management systems, this is like I was storing > BitKeeper in Git. That says I trust Git but not my own code. > > Has anyone proposed redoing the texinfo stuff in Groff? If not, why not? > Larry! Actually you proposed exactly that on this very mailing list in 2005 :-). I just happened to be reading through the archives last night... https://lists.gnu.org/archive/html/groff/2005-10/msg00107.html If you read through the thread following the above message there’s a lot of interesting commentary, which is still somehow just a relevant in 2022 as it was in 2005. Josh
Re: Warn on mid-input line sentence endings
Hi, I'm here with a quick tangent. It turns out that there is a lot of discourse out there about "semantic newlines", under a few different names. So far the names I've seen are: - One Sentence Per Line (OSPL) - Semantic Line Breaks (SemBr) - Semantic Linefeeds - Ventilated Prose - Semantic newlines (just on this list) Reading through the pages below was helpful in getting a better idea of what language people use to discuss this. They're mostly historical retrospectives or arguments for the merit of semantic newlines. https://rhodesmill.org/brandon/2012/one-sentence-per-line https://ramshankar.org/blog/posts/2019/semantic-line-breaks https://vanemden.wordpress.com/2009/01/01/ventilated-prose https://discuss.python.org/t/semantic-line-breaks/13874 https://discuss.python.org/t/one-sentence-per-line-for-peps-and-more/13920 https://sembr.org https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line (Actually I think one-sentence-per-line denotes something slightly different from semantic-line-breaks, not that I know what that difference is). Hope this is interesting, Josh
Re: Warn on mid-input line sentence endings
Hey Alex, Thanks a lot for the clarifications, I agree with your reasoning. On Mon, May 1, 2023 at 8:30 PM Alejandro Colomar wrote: > What is ventilated in the context of prose? Not too clear to me just by > reading dict(1). Regarding "Ventilated Prose", it's more of an endearing figure of speech than a technical categorization. Think of a hot stuffy room, and the transformation that occurs when you open the window and let in a cool breeze -- the room becomes well ventilated. So too with a stuffy paragraph. Here's a relevant passage about the origin of the phrase from https://vanemden.wordpress.com/2009/01/01/ventilated-prose, > In the 1930s Buckminster Fuller (he of the domes, but also of many other > things) was doing research for the Phelps Dodge Corporation. His boss could > not read Fuller’s reports, but found them perfectly intelligible when read > aloud by the author. > > For Fuller's own account, see below. > > [...] > > Though the [...] presentation had been developed under the close observation > of > the corporation’s Director of Research, my final written presentation of it > was declared by the Director to be incomprehensible. Disgruntled, I re-read > it carefully and returned to the Director saying, "Please listen to this," > and proceeded to read in spontaneously metered "doses" from my manuscript. > As I read I also watched for expressions of comprehension on the Director’s > face. The Director pondered each verbal dose, and when his face signalled > "that is clear" I would intuitively measure out the next portion. Finally, > the Director said, "Why don’t you write it that way?" I said, "I am > reading directly and without skipping from my original text"; so the > Director said, "It just doesn’t read that way." The explanation was that > the intuitive doses did not correspond to conventional syntax. > > When the re-written report was submitted, the Director said, "This is lucid, > but it is poetry, and I cannot possibly hand it to the President of the > Corporation for submission to the Board of Directors." I insisted that it > was obviously not poetry, since both he and I knew how I had chopped up a > conventional prose report. The Director said, "I am having two poets for > dinner tonight and I will take this to them and see what they say." He > returned the next day and said, "It’s too bad — it’s poetry." Sorry to drone on about it, I just think it's very amusing :). Josh
[Groff] [SWISH-E] ANNOUNCE: Sman 1.00 Released (indexer for man pages)
Hello Everyone: I've just released Sman version 1.00! Sman is a replacement for 'man -k' and 'apropos' based on Swish-e and Perl. Sman indexes the complete text of your system's man pages and provides a program to undate the index and perform fast searches on the index. Sman runs on all tested UNIX-like OS's and environments, including OS X, Linux, FreeBSD, Solaris, cygwin, and others. It's called 'sman' because it provides two programs, sman and sman-update, o search on and create indexes of man pages. This release fixes small bugs over 0.99. Sman can be installed through CPAN by typing: % sudo cpan Sman Sman 1.00 is now on CPAN at http://search.cpan.org/~joshr/Sman-1.00/ as well as on my website at http://joshr.com/src/sman it should also soon be on freshmeat at http://freshmeat.net/projects/sman/ Changes since version 0.99: 1.00 Thu May 04 2006 Removed spurious error message when using sman's -v option without a query Changed source & -V version string to show Swish-e capitalized as here Test current Swish-e version more carefully in Sman::Util More error output in sman's undocumented --Debug mode Cleanup up how we check for $SWISH::API::VERSION Touchups to formatting of Changes file Updated various dates to 2006 Tiny POD touchups Complete Sman Changelog: http://joshr.com/src/sman/Sman-1.00/Changes Please let me know if you have any comments or discover any bugs. Links for Sman are above! Thanks, Josh Rabinowitz http://joshr.com -- -- -- joshr Consulting http://joshr.com/ -- -- Josh Rabinowitz [EMAIL PROTECTED] -- -- SkateboardDirectory.com(tm) http://SkateboardDirectory.com/ -- ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff
