* Richard Kettlewell <invalid@invalid.invalid>
| Ralf Fassel <ralfixx@gmx.de> writes:
| > Why do you expect that if you tell tar to use a file named 'NumNotes'
| > that it should use a file named 'NumNotes.tar.gz' instead?
>
| The script they quoted does “tar -xf $1.tar.gz”, i.e. it adds .tar.gz.

Ah, sorry for the noise. Hadn't spotted that post.

| Presumably the script they are actually running is different.

Obviously it is, considering the tar message.
Should be trivial to 'type tarx' to find out instead of accusing tar of
lying (but creating conspiracy contexts where none exist seems en vogue
these days... :-()

R'

On 2024-06-12 21:16, Richard Kettlewell wrote:
> Ralf Fassel <ralfixx@gmx.de> writes:
>> * db <dieterhansbritz@gmail.com>
>> | ~/bin> tarx ../tarfiles/NumNotes
>> | tar (child): ../tarfiles/NumNotes: Cannot open: No such file or directory
>> --<snip-snip>--
>> | ~/bin> ls ../tarfiles/Num*
>> | ../tarfiles/NumNotes.tar.gz
>>>
>> | The last line proves that it's lying.
>>
>> Why do you expect that if you tell tar to use a file named 'NumNotes'
>> that it should use a file named 'NumNotes.tar.gz' instead?
>
> The script they quoted does “tar -xf $1.tar.gz”, i.e. it adds .tar.gz.

Thus it is not obeying the -x in bash.

>
> Presumably the script they are actually running is different.

Yes.

--
Cheers,
Carlos E.R.

On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:

> I like to make life easy so I wrote a one-line script for extracting the
> contents of a tar file. I copied it into the /bin directory so I can run
> it from anywhere.
> I tried it out in a test directory where I had it, and where there is a
> small test tar file. Here is the dialogue from running it, using both
> the local script and the one in /bin:
>
> ~/tartest> ls tarx test.tar.gz ~/tartest> cat tarx tar -xf $1.tar.gz
> ~/tartest> cat ~/bin/tarx tar -xf $1.tar.gz ~/tartest> ./tarx test
> ~/tartest> ls tarx test test.tar.gz ~/tartest> del -r test ~/tartest>
> tarx test tar (child): test: Cannot open: No such file or directory tar
> (child): Error is not recoverable: exiting now tar: Child returned
> status 2 tar: Error is not recoverable: exiting now
>
> Why doesn't it work from bin/ ?

Red face time.
I just found out that I have an alias called tarx in
my .bashrc. In fact, someone asked me about this and
I answered in the negative, without checking. My apologies!

--
db

On Fri, 14 Jun 2024 14:35:02 +0000, db wrote:

> On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:
>
>> I like to make life easy so I wrote a one-line script for extracting the
>> contents of a tar file. I copied it into the /bin directory so I can run
>> it from anywhere.
[snip]
>> Why doesn't it work from bin/ ?
>
> Red face time.
> I just found out that I have an alias called tarx in
> my .bashrc. In fact, someone asked me about this and
> I answered in the negative, without checking. My apologies!

Apology accepted. :-)

Glad you found (and presumably fixed) your problem.

--
Lew Pitcher
"In Skills We Trust"

On 2024-06-14 16:38, Lew Pitcher wrote:
> On Fri, 14 Jun 2024 14:35:02 +0000, db wrote:
>
>> On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:
>>
>>> I like to make life easy so I wrote a one-line script for extracting the
>>> contents of a tar file. I copied it into the /bin directory so I can run
>>> it from anywhere.
> [snip]
>>> Why doesn't it work from bin/ ?
>>
>> Red face time.
>> I just found out that I have an alias called tarx in
>> my .bashrc. In fact, someone asked me about this and
>> I answered in the negative, without checking. My apologies!
>
> Apology accepted. :-)
>
> Glad you found (and presumably fixed) your problem.

What command would show what exact incantation is used? Ie, what
path/binary, or what alias?

which tarx?

For instance:

cer@Telcontar:~> which l
which: no l in
(/home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/sbin:/usr/sbin)
cer@Telcontar:~>

But it is an alias in my system

--
Cheers, Carlos.

At Fri, 14 Jun 2024 19:42:40 +0200 "Carlos E.R." <robin_listas@es.invalid> wrote:

>
> On 2024-06-14 16:38, Lew Pitcher wrote:
> > On Fri, 14 Jun 2024 14:35:02 +0000, db wrote:
> >
> >> On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:
> >>
> >>> I like to make life easy so I wrote a one-line script for extracting the
> >>> contents of a tar file. I copied it into the /bin directory so I can run
> >>> it from anywhere.
> > [snip]
> >>> Why doesn't it work from bin/ ?
> >>
> >> Red face time.
> >> I just found out that I have an alias called tarx in
> >> my .bashrc. In fact, someone asked me about this and
> >> I answered in the negative, without checking. My apologies!
> >
> > Apology accepted. :-)
> >
> > Glad you found (and presumably fixed) your problem.
>
>
> What command would show what exact incantation is used? Ie, what
> path/binary, or what alias?
>
> which tarx?
>
>
> For instance:
>
> cer@Telcontar:~> which l
> which: no l in
> (/home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/sbin:/usr/sbin)
> cer@Telcontar:~>
>
>
> But it is an alias in my system

This depends on the shell...

marchhare% which dir
dir: aliased to ls -F -C
marchhare% echo $SHELL
/bin/tcsh

>
>
>

--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@deepsoft.com -- Webhosting Services

On 2024-06-14 1:42 p.m., Carlos E.R. wrote:
>
> What command would show what exact incantation is used? Ie, what
> path/binary, or what alias?
>
> which tarx?

If you're using Bash as your shell, the 'type' builtin command will tell
you. E.g.,

$ type ls
ls is aliased to `ls --color=auto'

On 2024-06-14 20:50, Robert Heller wrote:
> At Fri, 14 Jun 2024 19:42:40 +0200 "Carlos E.R." <robin_listas@es.invalid> wrote:

>> What command would show what exact incantation is used? Ie, what
>> path/binary, or what alias?
>>
>> which tarx?
>>
>>
>> For instance:
>>
>> cer@Telcontar:~> which l
>> which: no l in
>> (/home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/sbin:/usr/sbin)
>> cer@Telcontar:~>
>>
>>
>> But it is an alias in my system
>
> This depends on the shell...

The default bash :-)

>
> marchhare% which dir
> dir: aliased to ls -F -C
> marchhare% echo $SHELL
> /bin/tcsh

Interesting.

--
Cheers, Carlos.

On 2024-06-14 21:30, John-Paul Stewart wrote:
> On 2024-06-14 1:42 p.m., Carlos E.R. wrote:
>>
>> What command would show what exact incantation is used? Ie, what
>> path/binary, or what alias?
>>
>> which tarx?
>
> If you're using Bash as your shell, the 'type' builtin command will tell
> you. E.g.,
>
> $ type ls
> ls is aliased to `ls --color=auto'
>

Ah, yes. I knew about "type", but I don't use it. I will now.

cer@Telcontar:~> type l
l is aliased to `ls -alF'
cer@Telcontar:~> type ls
ls is aliased to `_ls'
cer@Telcontar:~> type _ls
_ls is a function
_ls ()
{ local IFS=' ';
command ls $LS_OPTIONS ${1+"$@"}
} cer@Telcontar:~>
cer@Telcontar:~> echo $LS_OPTIONS
-N --color=tty -T 0
cer@Telcontar:~>

--
Cheers, Carlos.

On Fri, 14 Jun 2024 18:50:02 +0000, Robert Heller wrote:

> At Fri, 14 Jun 2024 19:42:40 +0200 "Carlos E.R." <robin_listas@es.invalid> wrote:
>
>>
>> On 2024-06-14 16:38, Lew Pitcher wrote:
>> > On Fri, 14 Jun 2024 14:35:02 +0000, db wrote:
>> >
>> >> On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:
>> >>
>> >>> I like to make life easy so I wrote a one-line script for extracting the
>> >>> contents of a tar file. I copied it into the /bin directory so I can run
>> >>> it from anywhere.
>> > [snip]
>> >>> Why doesn't it work from bin/ ?
>> >>
>> >> Red face time.
>> >> I just found out that I have an alias called tarx in
>> >> my .bashrc. In fact, someone asked me about this and
>> >> I answered in the negative, without checking. My apologies!
>> >
>> > Apology accepted. :-)
>> >
>> > Glad you found (and presumably fixed) your problem.
>>
>>
>> What command would show what exact incantation is used? Ie, what
>> path/binary, or what alias?
>>
>> which tarx?
[snip]
>> But it is an alias in my system
>
> This depends on the shell...
>
> marchhare% which dir
> dir: aliased to ls -F -C
> marchhare% echo $SHELL
> /bin/tcsh

16:22:25 $ echo $SHELL
/bin/bash

16:22:28 $ alias
alias tarx='tar -xf'

bash(1) says
"Aliases are created and listed with the alias command,
and removed with the unalias command."

--
Lew Pitcher
"In Skills We Trust"

On Fri, 14 Jun 2024 20:24:53 +0000, Lew Pitcher wrote:

> On Fri, 14 Jun 2024 18:50:02 +0000, Robert Heller wrote:
>
>> At Fri, 14 Jun 2024 19:42:40 +0200 "Carlos E.R." <robin_listas@es.invalid> wrote:
>>
>>>
>>> On 2024-06-14 16:38, Lew Pitcher wrote:
>>> > On Fri, 14 Jun 2024 14:35:02 +0000, db wrote:
>>> >
>>> >> On Sun, 9 Jun 2024 14:36:49 -0000 (UTC), db wrote:
>>> >>
>>> >>> I like to make life easy so I wrote a one-line script for extracting the
>>> >>> contents of a tar file. I copied it into the /bin directory so I can run
>>> >>> it from anywhere.
>>> > [snip]
>>> >>> Why doesn't it work from bin/ ?
>>> >>
>>> >> Red face time.
>>> >> I just found out that I have an alias called tarx in
>>> >> my .bashrc. In fact, someone asked me about this and
>>> >> I answered in the negative, without checking. My apologies!
>>> >
>>> > Apology accepted. :-)
>>> >
>>> > Glad you found (and presumably fixed) your problem.
>>>
>>>
>>> What command would show what exact incantation is used? Ie, what
>>> path/binary, or what alias?
>>>
>>> which tarx?
> [snip]
>>> But it is an alias in my system
>>
>> This depends on the shell...
>>
>> marchhare% which dir
>> dir: aliased to ls -F -C
>> marchhare% echo $SHELL
>> /bin/tcsh
>
> 16:22:25 $ echo $SHELL
> /bin/bash
>
> 16:22:28 $ alias
> alias tarx='tar -xf'
>
> bash(1) says
> "Aliases are created and listed with the alias command,
> and removed with the unalias command."

POSIX says
"A valid alias name shall be one that has been defined by
the alias utility and not subsequently undefined using
unalias."
(https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_03_01)
and further says (in regard to the alias utility)
"The alias utility shall create or redefine alias definitions
or write the values of existing alias definitions to standard
output."
(https://pubs.opengroup.org/onlinepubs/9699919799/utilities/alias.html)

So, it appears that bash conforms to POSIX requirements with
respect to the behaviour of it's "alias" builtin command.

--
Lew Pitcher
"In Skills We Trust"

On 2024-06-14 22:24, Lew Pitcher wrote:
> On Fri, 14 Jun 2024 18:50:02 +0000, Robert Heller wrote:
>
>> At Fri, 14 Jun 2024 19:42:40 +0200 "Carlos E.R." <robin_listas@es.invalid> wrote:

....

>>> What command would show what exact incantation is used? Ie, what
>>> path/binary, or what alias?
>>>
>>> which tarx?
> [snip]
>>> But it is an alias in my system
>>
>> This depends on the shell...
>>
>> marchhare% which dir
>> dir: aliased to ls -F -C
>> marchhare% echo $SHELL
>> /bin/tcsh
>
> 16:22:25 $ echo $SHELL
> /bin/bash
>
> 16:22:28 $ alias
> alias tarx='tar -xf'

Yes, this confirms that it is an alias, but the question was rather how
to find that a particular incantation by the user runs what.

is it (tarx or whatever) a command in some path, or is it an alias?
"type" does that.

--
Cheers, Carlos.

On Fri, 14 Jun 2024 18:50:02 +0000, Robert Heller wrote:

> marchhare% which dir
> dir: aliased to ls -F -C
> marchhare% echo $SHELL
> /bin/tcsh

I don’t think it’s specified by POSIX. bash has the “type” builtin which,
being builtin, can report on whether a given command is itself a builtin
or alias or function or an external executable.

On Fri, 14 Jun 2024 22:02:01 +0200, Carlos E.R. wrote:

> I knew about "type", but I don't use it.

In bash, “help type” will tell you all about it.

On Fri, 14 Jun 2024 20:24:53 -0000 (UTC), Lew Pitcher wrote:

> bash(1) says
> "Aliases are created and listed with the alias command,
> and removed with the unalias command."

Functions are more powerful than aliases. They can take arguments and run
entire command sequences, all within the current shell process.