Hi folks,
Raw escape characters (U+001B) get stripped from source-code during
formatting, but inserting one is still possible using \N'27':
\N'27'[4mI don't remember underlining this.\N'27'[0m
This has potential security implications for people using `less -R` (and
can still mess up terminal out
Sorry, the macros I've written are .strchr and .strrchr.
.index should not be too hard using direct method (KMP is too
complicated). I may have time to try, no promises...
On Sat, 25 Jul 2020 17:42:17 -0700strrchr
B 9 wrote:
> "Denis M. Wilson" wrote:
>
> > To implement .index as a macro one
> You misunderstand. Some people don't *want* to unite. Some might actively
> resist an attempt at "unification".
you're right: i don't get it and never will (especially when there are
so few people rely on for maintaining stuff).
regards
marc
> yes. but it doesn't mean we can't unite at some point
You misunderstand. Some people don't *want* to unite. Some might actively
resist an attempt at "unification".
On Mon, 27 Jul 2020 at 18:50, Marc Chantreux wrote:
> > Lack of "unity" is part of what makes open source what it is.
>
> yes. b
> Lack of "unity" is part of what makes open source what it is.
yes. but it doesn't mean we can't unite at some point. that's why i was
asking.
regards.
marc
> sed /^$/d will wipe empty lines wherever they're found, instead of only
> removing those at the end of a document.
ohh .. indeed. i have to admit i don't use sed for this kind of flow
control because i try to keep my scripts as simple as possible so my
move over it would has been
tac | awk
Even if the entire world agreed on licensing, there'd still be
disagreements about implementation or philosophy.
Lack of "unity" is part of what makes open source what it is.
On Mon, 27 Jul 2020 at 07:34, Marc Chantreux wrote:
> hello Ingo,
>
> thanks for this detailed anwser.
>
> > The reason
> and yet i'm confused: can you explain the benefit of it over my simple
> and working sed '/^$/d' ?
sed /^$/d will wipe empty lines wherever they're found, instead of only
removing those at the end of a document.
Many man(1) implementations deliberately "squeeze" empty lines to improve
the displ
hello John,
On Sat, Jul 25, 2020 at 02:57:13PM +1000, John Gardner wrote:
> >
> > also: i need "sed '/^$/q'" at the end of my filter because groff
> > renders a lot of empty lines at the end of the output whenever i
> > use b in my tbl format. i don't know how to remove it.
> sed -e :a -e '/^\n*$
hello,
> I don't understand how empty lines at the end can be related
> to making things bold (which is what "b" is supposed to do).
you're right: it happens every time.
> I suspect it is because of page length, with groff outputting
> the empty part of an only partially filled page at the end.
10 matches
Mail list logo
