unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Guile User <guile-user@gnu.org>, Chris Marusich <cmmarusich@gmail.com>
Subject: Re: How to get the preferred environment variable path separator?
Date: Mon, 28 Mar 2016 11:40:52 -0400	[thread overview]
Message-ID: <CAJ=RwfbOrdg6vmOWJZoZ5MK2pYC53-hEpoJoax03QOPXdnnaLw@mail.gmail.com> (raw)
In-Reply-To: <83lh52y5q6.fsf@gnu.org>

On Mon, Mar 28, 2016 at 11:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 28 Mar 2016 10:24:56 -0400
>> From: "Thompson, David" <dthompson2@worcester.edu>
>> Cc: Guile User <guile-user@gnu.org>, Chris Marusich <cmmarusich@gmail.com>
>>
>> The environment variable path separator is *not* defined depending on
>> the OS.  It is up to the programs that interpret these search paths to
>> specify what the separator should be.  ":" is the most common
>> separator, but that is just convention.  A search path is opaque to
>> the operating system, where environment variables are just strings
>> with no inherent meaning.
>
> We are not talking about the OS, we are talking about the programs
> that set and query environment variables using 'getenv', 'putenv', and
> other similar APIs, followed by simple string processing.  And those
> are definitely _not_ treating the separator as opaque, something you
> can easily verify both by looking at the sources of the respective
> applications, and by simple experiments.
>
> And in that sense, the path separator character is always ':' on Posix
> systems and ';' on MS-Windows.  So I think Guile ought to have such a
> variable; Emacs, for one, does.

OK, sure.



  reply	other threads:[~2016-03-28 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28  0:42 How to get the preferred environment variable path separator? Chris Marusich
2016-03-28 10:00 ` Alex Vong
2016-03-28 12:20   ` Thompson, David
2016-03-28 13:46     ` Alex Vong
2016-03-28 14:24       ` Thompson, David
2016-03-28 15:36         ` Paul Smith
2016-03-28 15:36         ` Eli Zaretskii
2016-03-28 15:40           ` Thompson, David [this message]
2016-03-29  7:53           ` tomas
2016-03-31  4:38         ` Chris Marusich

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfbOrdg6vmOWJZoZ5MK2pYC53-hEpoJoax03QOPXdnnaLw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=cmmarusich@gmail.com \
    --cc=eliz@gnu.org \
    --cc=guile-user@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).