Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security -Wall
uname output: Linux EliteBook 5.11.0-25-generic #27-Ubuntu SMP Fri Jul
9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Machine
I am trying to use getopts so one of the options can use an optional argument.
Have seen many discussions online about using getopts to handle options with
optional arguments,
But also a lot of confusing arguments against many workarounds. Could bash
getopts have a natural
way to introduce an
Date:Fri, 27 Aug 2021 15:05:52 +
From:nigelberlinguer via Bug reports for the GNU Bourne Again SHell
Message-ID:
<0IgsinjPxg5VSubCxyc64u9axdDTEubUNcQFmIaPyduotl2CyQ9g71uoLtpmXL2hUph1_eHzVRnEZ7vyyHFKqqy3OlPydQXccd2CkHyzpjA=@protonmail.com>
| I am trying to use
On Fri, Aug 27, 2021, at 1:20 PM, nigelberlinguer wrote:
> ‐‐‐ Original Message ‐‐‐
> On Friday, August 27, 2021 4:02 PM, Robert Elz wrote:
> > XBD 12.2 guideline 7 is:
> >
> > Guideline 7: Option-arguments should not be optional.
> >
> > That is, if you want to be able to give an option
‐‐‐ Original Message ‐‐‐
On Friday, August 27, 2021 4:02 PM, Robert Elz wrote:
> Date:Fri, 27 Aug 2021 15:05:52 +
> From:nigelberlinguer via Bug reports for the GNU Bourne Again
> SHell
>
> Message-ID:
>
‐‐‐ Original Message ‐‐‐
On Friday, August 27, 2021 8:52 PM, Robert Elz wrote:
> Date:Fri, 27 Aug 2021 17:20:39 +
> From:nigelberlinguer
>
> Message-ID:
>
>
>
> | It should be noted though, that the POSIX requirement by "Guideline 7"
> | is not guided
‐‐‐ Original Message ‐‐‐
On Friday, August 27, 2021 8:52 PM, Robert Elz wrote:
> Date:Fri, 27 Aug 2021 17:20:39 +
> From:nigelberlinguer
>
> Message-ID:
>
>
>
> | It should be noted though, that the POSIX requirement by "Guideline 7"
> | is not guided
Hyunho Cho writes:
> If i enter a command line like below then '>' prompt appears for the
> input of here document.
>
> bash$ { cat <<\@ > foo ;} 2> /dev/null
>> 111
>> 222 # '>' prompt
>> @
>
>
> but if i use alias then '>' prompt does not appear and default bash
> prompt
On 8/27/21, 4:09 PM, Chet Ramey wrote:
Thanks for the report. That circumstance is a pathname consisting
solely of
one or more slashes, separated from the previous word by whitespace. I'll
fix it.
Awesome! :-D
PS — Another pathological test case is, e.g.:
ls / / / //
The code
On 8/26/21 10:18 PM, d...@dabe.com wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
Description:
The manpage for bash(1) says:
unix-filename-rubout
Kill the word behind point, ***USING WHITE SPACE AND THE SLASH
CHARACTER AS THE
Date:Fri, 27 Aug 2021 17:20:39 +
From:nigelberlinguer
Message-ID:
| It should be noted though, that the POSIX requirement by "Guideline 7"
| is not guided by actual portability in the technical sense but by a
| rule written in the POSIX standard.
Those
On Fri, Aug 27, 2021 at 11:33 AM Lawrence Velázquez wrote:
>
> On Fri, Aug 27, 2021, at 1:20 PM, nigelberlinguer wrote:
> > ‐‐‐ Original Message ‐‐‐
> > On Friday, August 27, 2021 4:02 PM, Robert Elz wrote:
> > > XBD 12.2 guideline 7 is:
> > >
> > > Guideline 7: Option-arguments should
12 matches
Mail list logo
