From: Michael Slass <miknrene@drizzle.com>
Subject: Re: Autosave and filename too long
Date: Thu, 24 Oct 2002 17:03:41 GMT [thread overview]
Message-ID: <m365vr22ak.fsf@localhost.localdomain> (raw)
In-Reply-To: _DOt9.20721$DP6.65383@news-server.bigpond.net.au
>> "Matt Muggeridge" <Matt.Muggeridge@hp.com> writes:
>>
>> I would like to try changing the "#" character to learn if it makes
>> a difference.
>>
>> Thanks,
>> Matt.
>>
>>
>>"Michael Slass" <miknrene@drizzle.com> wrote in message
>>news:m33cqwqufe.fsf@localhost.localdomain...
>>
>> (defadvice make-auto-save-file-name (after auto-save-remove-hash-mark ())
>> "return an autosave file name, replacing \"#\" with \"OCTOTHORPE\""
>> (setq ad-return-value
>> (replace-regexp-in-string "#" "OCTOTHORPE" ad-return-value)))
>>
>> (ad-activate 'make-auto-save-file-name)
>>
>>
>> (defun auto-save-file-name-p (filename)
>> "Return non-nil if FILENAME can be yielded by `make-auto-save-file-name'.
>> FILENAME should lack slashes. You can redefine this for customization."
>> (string-match "^OCTOTHORPE.*OCTOTHORPE$" filename))
"Matt Muggeridge" <Matt.Muggeridge@hp.com> writes:
>Michael,
>
>Thanks for making the octothorpe go away! The auto-save feature is now
>working.
>
>On to the next hurdle...
>
>The recover feature of emacs is still searching for files of name #foo.c#.
>So after a quick test, I tried to recover foo.c (I first verifed the
>contents of "OCTOTHORPEfoo.cOCTOTHORPE" existed and contained 'lost' edits).
>The recover operation complained with:
>
> Auto-save file /usr/users/muggerid/kingsx/#foo.c# not current
>
>Now that auto-save is working, what is needed to make recover aware of this
>new auto-save file name format?
>
>Matt.
Hmmm... I'm not sure why that is, since recover-file uses
make-auto-save-file-name to generate the recovery file name, so it
should match. I'll keep looking at it, but perhaps one of the gurus
might have an idea?
--
Mike Slass
next prev parent reply other threads:[~2002-10-24 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 5:22 Autosave and filename too long Michael Slass
2002-10-24 8:59 ` Matt Muggeridge
2002-10-24 17:03 ` Michael Slass [this message]
2002-11-01 1:48 ` Matt Muggeridge
2002-11-01 2:23 ` Michael Slass
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 1:13 Matt Muggeridge
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=m365vr22ak.fsf@localhost.localdomain \
--to=miknrene@drizzle.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.