Re: printf(1), sh(1), POSIX.2 and octal escape sequences

To: kre%munnari.OZ.AU@localhost, tlaronde%polynum.com@localhost
Subject: Re: printf(1), sh(1), POSIX.2 and octal escape sequences
From: neitzel%hackett.marshlabs.gaertner.de@localhost (Martin Neitzel)
Date: Fri, 30 Jun 2023 21:03:17 +0200 (CEST)

KRE> It depends upon the usage.   But if you're processing escapes, you
KRE> need to also process \\ to mean a literal '\' of course,  [...]

Not necessarily -- '\134' would be good enough :-)

Just joking, of course.  The weekend is nigh.

						Martin Neitzel

References:
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: tlaronde
- printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: tlaronde
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: RVP
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: tlaronde
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: Martin Husemann
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: tlaronde
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: Martin Husemann
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: tlaronde
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: David Holland
- Re: printf(1), sh(1), POSIX.2 and octal escape sequences
  - From: Robert Elz

Prev by Date: Trivial program size inflation
Next by Date: Re: old style tail(1) options and bin/57483
Previous by Thread: Re: printf(1), sh(1), POSIX.2 and octal escape sequences
Next by Thread: Re: printf(1), sh(1), POSIX.2 and octal escape sequences
Indexes:

Home | Main Index | Thread Index | Old Index