From: Eli Zaretskii <eliz@gnu.org>
To: Nathaniel Flath <flat0103@gmail.com>
Cc: jan.kratochvil@redhat.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] cd command defaults to ~
Date: Sun, 22 Jul 2012 17:13:00 -0000 [thread overview]
Message-ID: <837gtv1zz5.fsf@gnu.org> (raw)
In-Reply-To: <CAPrg3HA+mpqmBOLkhShuCm_HK0dRqfrZ=vTpfMG3cq2R_ANFNA@mail.gmail.com>
> Date: Sun, 22 Jul 2012 09:37:04 -0700
> From: Nathaniel Flath <flat0103@gmail.com>
>
> index: NEWS
> ===================================================================
> RCS file: /cvs/src/src/gdb/NEWS,v
> retrieving revision 1.533
> diff -u -r1.533 NEWS
> --- NEWS 4 Jul 2012 20:49:56 -0000 1.533
> +++ NEWS 7 Jul 2012 04:28:05 -0000
> @@ -3,6 +3,8 @@
>
> *** Changes since GDB 7.4
>
> +* The 'cd' command now defaults to using '~' if not given an argument.
OK, but since not everyone is born knowing what '~' means (think
Windows users), I would suggest a small correction:
The 'cd' command now defaults to using '~' (the home directory) if
not given an argument.
> @kindex cd
> @cindex change working directory
> @item cd @var{directory}
As Jan points out, the DIRECTORY part is now optional, which we
express by [...]. So:
@item cd @r{[}@var{directory}@r{]}
(The @r{} parts are needed to countermand the default @code formatting
of the @item line.)
> -Set the @value{GDBN} working directory to @var{directory}.
> +Set the @value{GDBN} working directory to @var{directory}. If given no
> +arguments, uses '~'.
"~" is a file name, so please use @file{~} instead of quoting it.
Also, I would replace the last sentence with
If not given, @var{directory} defaults to @file{~}.
OK with those changes.
Thanks.
prev parent reply other threads:[~2012-07-22 17:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 2:31 Nathaniel Flath
2012-07-05 14:00 ` Jan Kratochvil
2012-07-05 17:34 ` Nathaniel Flath
2012-07-05 17:50 ` Eli Zaretskii
2012-07-05 18:09 ` Tom Tromey
2012-07-07 4:29 ` Nathaniel Flath
2012-07-07 6:17 ` Jan Kratochvil
[not found] ` <CAPrg3HBCBs5tmuM9qH=Q=_PgPVb8Rb-=fbPX_ZSy1dEWgKcY9g@mail.gmail.com>
[not found] ` <20120722163408.GA20790@host2.jankratochvil.net>
2012-07-22 16:37 ` Nathaniel Flath
2012-07-22 16:50 ` Jan Kratochvil
2012-07-23 7:42 ` Sergio Durigan Junior
2012-07-23 14:14 ` Tom Tromey
2012-08-04 5:55 ` Nathaniel Flath
2012-08-04 6:05 ` Sergio Durigan Junior
2012-08-04 7:11 ` Eli Zaretskii
2012-08-04 17:10 ` Nathaniel Flath
2012-08-04 17:16 ` Eli Zaretskii
2012-08-04 18:16 ` Nathaniel Flath
2012-08-04 18:28 ` Jan Kratochvil
[not found] ` <CAPrg3HDpFytQmCHe2GSzW=_ckAcNXN5UPJ5qPWDPHgwzY8RWzw@mail.gmail.com>
2012-08-06 9:15 ` Nathaniel Flath
2012-08-06 18:43 ` [commit] " Jan Kratochvil
2012-08-07 5:52 ` [obv] testsuite: default.exp: Fix cd regression [Re: [commit] [PATCH] cd command defaults to ~] Jan Kratochvil
2012-08-07 7:31 ` [commit] [PATCH] cd command defaults to ~ Nathaniel Flath
2012-08-07 7:53 ` Jan Kratochvil
2012-08-07 16:02 ` Nathaniel Flath
2012-07-22 17:13 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837gtv1zz5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=flat0103@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox