On 8/27/21, 5:22 PM, Dabrien 'Dabe' Murphy wrote:
On 8/27/21, 4:09 PM, Chet Ramey wrote:
That circumstance is a pathname consisting solely of one or more
slashes,
separated from the previous word by whitespace. I'll fix it.
The code has been like this since January, 2004. That's pretty
Hi Team,
Could I get some help locating portions of the code that would need
to be tweaked to add these features?
If I had the time, I would love to get to know the code, but I have too
much going on in my real job.
1. Intelligent support for !$ (and related - like !2$, !-N, etc) : This
On Tue, Aug 31, 2021, at 4:02 AM, Lawrence Velázquez wrote:
> ksh does not blindly remove all leading whitespace
For the curious, this is how ksh(1) describes it:
If '#' is appended to '<<', then leading spaces and tabs
will be stripped off the first line of the document and up
31 Ağustos 2021 Salı tarihinde Jesse Hathaway yazdı:
> On Tue, Aug 31, 2021 at 2:24 AM Přemysl Šťastný wrote:
> >
> > Thanks for advice. How do you use it in more detail please?
>
> You can feed shfmt an individual file to format, it defaults to
> using tabs for indentation:
>
> $ shfmt
On Tue, Aug 31, 2021 at 2:24 AM Přemysl Šťastný wrote:
>
> Thanks for advice. How do you use it in more detail please?
You can feed shfmt an individual file to format, it defaults to
using tabs for indentation:
$ shfmt ~/test.sh
#!/bin/bash
cat <<-EOF
hello!
EOF
Or you can
On 8/27/21 9:47 PM, Dale R. Worley wrote:
Hyunho Cho writes:
but if i use alias then '>' prompt does not appear and default bash
prompt appears
bash$ alias myalias='{ cat <<\@ > foo ;} 2> /dev/null'
bash$ myalias
bash$ 111
bash$ 222 # bash$ prompt
bash$ @
I don't know the
Hi,
> ... ignoring both leading spaces and leading tabs. eg.
Something like (there must be nothing but tabulation before closing ``EOF'')?
func(){
sed 's/^ \{2\}//' <<- EOF
blabla
EOF
}
Depending on how and why, there is a lot of *variants*:
- leading spaces and/or/not
> On Aug 31, 2021, at 3:16 AM, Přemysl Šťastný wrote:
>
> I didn't realize yesterday, that ksh93 is not a nick name, but ksh version
> 93. :D
Sort of.
> So it would be okey with you, if I try to implement it using <<#?
The bash maintainer (who is not me) hasn’t yet indicated whether this is
Thanks for advice. How do you use it in more detail please?
On 8/30/21 11:48 PM, Jesse Hathaway wrote:
Will ksh93 version ever get to upstream? This ugly 'bug' is here for
decades and really irritates me and many people, who ever used shell for
larger scripting and don't like to use tabs.
I
I didn't realize yesterday, that ksh93 is not a nick name, but ksh
version 93. :D
So it would be okey with you, if I try to implement it using <<#?
Is there any git repo of bash?
Thanks.
P.
On 8/30/21 11:43 PM, Lawrence Velázquez wrote:
On Mon, Aug 30, 2021, at 5:22 PM, Přemysl Šťastný
10 matches
Mail list logo
