From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yegor Timoshenko <yegortimoshenko@gmail.com>, 29122@debbugs.gnu.org
Subject: bug#29122: eshell passes ARGV[0] as full path to executable
Date: Tue, 12 Dec 2017 22:29:35 -0500 [thread overview]
Message-ID: <87fu8fcnkw.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83tvybvfx9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 03 Nov 2017 12:02:10 +0200")
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 parent reply other threads:[~2017-12-13 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 7:33 bug#29122: eshell passes ARGV[0] as full path to executable Yegor Timoshenko
2017-11-03 8:30 ` Noam Postavsky
2017-11-03 8:54 ` Eli Zaretskii
[not found] ` <CAF4sQCM56=6y=1Lrg9RAQo+ui2kRSqRVHiarYYX=i6FGDv3C_A@mail.gmail.com>
2017-11-03 10:02 ` Eli Zaretskii
2017-12-13 3:29 ` Noam Postavsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu8fcnkw.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=29122@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yegortimoshenko@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).