From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: On DOS/Windows, unnecessary load of tramp by `file-relative-name'
Date: Wed, 30 Apr 2003 10:21:23 +0200 [thread overview]
Message-ID: <84of2os8e4.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <200304292138.h3TLcjcK007617@rum.cs.yale.edu> (Stefan Monnier's message of "Tue, 29 Apr 2003 17:38:44 -0400")
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
> I suspect the four lines should purely and simply be removed.
Indeed.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-30 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 10:54 On DOS/Windows, unnecessary load of tramp by `file-relative-name' David PONCE
2003-04-24 14:12 ` Kai Großjohann
2003-04-29 21:38 ` Stefan Monnier
2003-04-30 8:21 ` Kai Großjohann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 14:44 David PONCE
2003-04-25 13:23 ` Kai Großjohann
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84of2os8e4.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).