From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: desktop and tilde-expand-file-name
Date: Sun, 29 Dec 2002 12:45:08 +0100 [thread overview]
Message-ID: <843cohxd4r.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: 3E0EBCFE.8090106@math.ku.dk
Lars Hansen <larsh@math.ku.dk> writes:
> 1. How do I do? I have not participated in Emacs development before,
> and I don't have CVS.
I think CVS is necessary. It's not that difficult to use.
Basically, you go to the Emacs project page on Savannah, then you
click on CVS and this explains read-only anon-cvs access.
Once you have a working directory according to the instructions
there, `cd' into it and do `cvs update -dP' to fetch the most recent
changes from the server. Do `cvs diff -u' (or `cvs diff -c'
depending on taste) to get the difference between your changed
version and the server.
After `cvs update -dP', you might get `conflicts'. Look at the
corresponding files for `===' -- you will easily see the conflict
markers. Merge the two versions in a way that seems sensible and
remove the conflict markers.
> 2. For use in the desktop module, I need a function
> `tilde-expand-file-name' that should work like `expand-file-name'
> except that path is specified from "~" rather than from root when
> that is possible.
Maybe abbreviate-file-name is what you are looking for?
--
Ambibibentists unite!
next prev parent reply other threads:[~2002-12-29 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 9:14 desktop and tilde-expand-file-name Lars Hansen
2002-12-29 11:45 ` Kai Großjohann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-18 22:04 Lars Hansen
2003-02-19 0:01 ` Kim F. Storm
2003-02-19 9:22 ` Lars Hansen
[not found] ` <84heb0wnc9.fsf@lucy.is.informatik.uni-duisburg.de>
2003-02-19 11:09 ` Lars Hansen
2003-02-19 15:43 ` Reiner Steib
2003-02-19 17:18 ` Lars Hansen
2003-02-19 18:57 ` Kim F. Storm
2003-02-19 20:54 ` Lars Hansen
2003-02-19 10:51 ` Richard Stallman
2003-02-19 10:56 ` Lars Hansen
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=843cohxd4r.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).