From: Stephen Peters <speters%samsun@us.oracle.com>
Subject: Re: Incoming mail and on-the-fly compression
Date: 20 May 1996 14:35:09 -0700 [thread overview]
Message-ID: <r3epw7z110y.fsf@samsun.us.oracle.com> (raw)
In-Reply-To: Mark Borges's message of 20 May 1996 13:16:51 -0600
Mark Borges <mdb@cdc.noaa.gov> writes:
> >> On 19 May 1996 21:16:45 -0400,
> >> Richard Pieri(rp) wrote:
> >>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>
> LMI> I didn't know that `make-temp-name' creates names like that. What
> LMI> system is this on?
>
> rp> Sparc Sun Solaris 2.5, XEmacs 19.13, Gnus 5.0.15.
>
> Sparc Sun Solaris 2.5, XEmacs 19.14, sgnus-0.89
>
> doesn't:
>
> (make-temp-name "foo") ==> "fooa005QB"
Actually, it probably does.
Because make-temp-name uses the mktemp() function (in Emacs 19, and I
would assume in XEmacs as well), this is kind of system-specific. On
Solaris 2.5, it appears that the set of characters used for those last
6 positions can include both the period (.) and the underscore (_)
characters as well as the alphanumeric characters (bringing the number
of characters used to 64 -- probably for efficiency considerations).
On the other hand, the GNU C library only uses letters and digits in
its implementation. I will leave the behavior of other systems as an
exercise for the reader.
In short, on some machines it's quite possible to see temp files
ending in ".Z" or ".gz", or even any other special one- or
two-character extension.
--
Stephen L. Peters speters%samsun@us.oracle.com
For PGP key, use keyservers or send email with subject: SEND PGP KEY
PGP fingerprint: BFA4 D0CF 8925 08AE 0CA5 CCDD 343D 6AC6
Oracle won't speak for me, so I won't speak for them.
next prev parent reply other threads:[~1996-05-20 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-14 13:18 Richard Pieri
1996-05-19 16:20 ` Lars Magne Ingebrigtsen
1996-05-20 1:16 ` Richard Pieri
1996-05-20 19:16 ` Mark Borges
1996-05-20 21:35 ` Stephen Peters [this message]
1996-05-20 22:28 ` Lars Magne Ingebrigtsen
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=r3epw7z110y.fsf@samsun.us.oracle.com \
--to=speters%samsun@us.oracle.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;
as well as URLs for NNTP newsgroup(s).