From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Backing up abbrev_defs?
Date: Tue, 30 Jul 2019 16:12:17 +0100 [thread overview]
Message-ID: <8736inpne6.fsf@skimble.plus.com> (raw)
In-Reply-To: <83zhkvin8k.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Jul 2019 17:57:31 +0300")
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Sharon Kimble <boudiccas@skimble.plus.com>
>> Date: Tue, 30 Jul 2019 14:37:57 +0100
>>
>> I want to backup my abbrev_defs file exactly the same as everything else is backed up, i.e. when
>> there is a change to it, a backup is triggered to save it in ~/.emacs.d/backups. Although the
>> position is slightly complicated as its not normally open in any buffer, so the backup would
>> presumably have to be triggered on the source files changing.
>>
>> I've googled but haven't found any instances of it being backed up, so there isn't anything
>> seemingly available for me to hack from or with. So can some kind soul help with some working
>> code, or guidance to a non-programmer to achieve this please?
>
> I don't understand the question. Are you saying that when you save
> your abbrevs, Emacs doesn't create a backup file for abbrev_defs, as
> it does for any other file you save?
No! No backup created from it at all! Which I found was rather strange, hence my request.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 10.0, fluxbox 1.3.7, emacs 26.2, org 9.2.4
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-07-30 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 13:37 Backing up abbrev_defs? Sharon Kimble
2019-07-30 14:57 ` Eli Zaretskii
2019-07-30 15:12 ` Sharon Kimble [this message]
2019-07-30 15:38 ` Eli Zaretskii
2019-07-30 21:07 ` Sharon Kimble
2019-08-02 9:13 ` Eli Zaretskii
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=8736inpne6.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).