From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Implement multi-component --with-auto-load-dir
Date: Wed, 09 May 2012 17:50:00 -0000 [thread overview]
Message-ID: <834nrp1c2s.fsf@gnu.org> (raw)
In-Reply-To: <20120509154847.GB12692@host2.jankratochvil.net>
> Date: Wed, 9 May 2012 17:48:47 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> +set auto-load scripts-directory <dir1>[:<dir2>...]
> + Set a list of directories with auto-loaded scripts. Automatically
"Set a list of directories from which to load auto-loaded scripts."
> +Set the list of directories with auto-loaded scripts."), _("\
> +Show the list of directories with auto-loaded scripts."), _("\
Likewise here.
> +may be delimited by the host platform directory separator in use.
I believe the correct term is "path separator". I suggest to say
(@samp{:} on Unix, @samp{;} on Windows and DOS)
for clarity here, and not further down.
> +Each entry here needs to be covered also by the security setting
> +@xref{set auto-load safe-path}.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You want "(@pxref{...})" here.
OK with these changes.
Thanks.
next prev parent reply other threads:[~2012-05-09 17:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 15:49 Jan Kratochvil
2012-05-09 17:50 ` Eli Zaretskii [this message]
2012-05-09 18:04 ` Jan Kratochvil
2012-05-09 18:45 ` Eli Zaretskii
2012-05-09 18:44 ` [doc patch] path vs. directory separator [Re: [patch 2/2] Implement multi-component --with-auto-load-dir] Jan Kratochvil
2012-05-09 19:21 ` Eli Zaretskii
2012-05-09 19:30 ` [commit] " Jan Kratochvil
2012-05-09 18:55 ` [patch 2/2] Implement multi-component --with-auto-load-dir Jan Kratochvil
2012-05-09 19:23 ` Eli Zaretskii
2012-05-11 18:21 ` [commit] " Jan Kratochvil
2012-05-09 20:18 ` Joel Brobecker
2012-05-09 20:34 ` Jan Kratochvil
2012-05-09 20:51 ` Joel Brobecker
2012-05-11 18:47 ` Jan Kratochvil
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=834nrp1c2s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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