From: John Owens <john_owens@yahoo.com>
Subject: Re: OS X (or other OS's): how to get a fully-qualified domain name?
Date: Tue, 27 Jul 2004 18:29:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20040727T202534-855@post.gmane.org> (raw)
In-Reply-To: jwvacxlcorp.fsf-monnier+gnu.emacs.help@gnu.org
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> The Message-ID can use anything you want, so long as it obeys similar
> constraints to the ones applied to host names.
> I'd guess that youremail <at> address plus some time-dependent string is
> sufficient for uniqueness since noone else will use youremail <at> address even
> on some other machine.
And I think that's my best bet ... thanks to all for the advice on this.
This does bring up the larger point, however, that there might be circumstances
where emacs DOES need to know its fully qualified domain name, and there does
not seem to be a way to get it, which is unfortunate.
JDO
next prev parent reply other threads:[~2004-07-27 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1622.1090879447.1960.help-gnu-emacs@gnu.org>
2004-07-26 23:11 ` OS X (or other OS's): how to get a fully-qualified domain name? Kevin Rodgers
2004-07-26 23:59 ` John Owens
[not found] ` <mailman.1631.1090886583.1960.help-gnu-emacs@gnu.org>
2004-07-27 1:22 ` Barry Margolin
2004-07-27 1:37 ` John Owens
[not found] ` <mailman.1641.1090892436.1960.help-gnu-emacs@gnu.org>
2004-07-27 15:16 ` Stefan Monnier
2004-07-27 17:03 ` John Owens
[not found] ` <mailman.1759.1090947989.1960.help-gnu-emacs@gnu.org>
2004-07-27 18:06 ` Stefan Monnier
2004-07-27 18:29 ` John Owens [this message]
[not found] ` <mailman.1770.1090954587.1960.help-gnu-emacs@gnu.org>
2004-07-27 19:46 ` Stefan Monnier
2004-07-27 20:30 ` John Owens
2004-07-27 19:48 ` Kevin Rodgers
2004-07-27 20:49 ` John Owens
2004-07-26 21:59 John Owens
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=loom.20040727T202534-855@post.gmane.org \
--to=john_owens@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.