[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29122: eshell passes ARGV[0] as full path to executable
From: |
Noam Postavsky |
Subject: |
bug#29122: eshell passes ARGV[0] as full path to executable |
Date: |
Tue, 12 Dec 2017 22:29:35 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) |
tags 29122 wontfix
close 29122
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Yegor Timoshenko <yegortimoshenko@gmail.com>
>> Date: Fri, 3 Nov 2017 09:22:59 +0000
>>
>> The use case here is when programs print usage information.
>>
>> Usage: ./a.out command [arguments...]
>> Usage: /home/user/path/to/a.out command [arguments...]
>>
>> The former reads better and is generally expected from shells.
>
> You will get the same problem when a.out is found by searching PATH.
> And on Windows, your program will almost always get argv[0] in
> absolute form. So you need to take care of that anyway, or else your
> program will sometimes produce that less readable output.
Therefore closing as wontfix.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#29122: eshell passes ARGV[0] as full path to executable,
Noam Postavsky <=