From: filebat Mark <filebat.mark@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: lost my abbrev-defs file
Date: Mon, 26 Apr 2010 13:28:59 +0800 [thread overview]
Message-ID: <r2zb93cb5f31004252228m2caf06c7y4a966c773353898d@mail.gmail.com> (raw)
In-Reply-To: <u2of22f52181004251958zcdd174f5p83064d83060ea0cf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Hi Matt
This is really pathetic! My abbrev file is quite personal, so it shall be
useless to you.
As for backup, I strongly recommend you to use dropbox + svn/git.
# dropbox is a wonderful online storage: support versioning, 2 GB free
capacity, high liability and easy to use.
https://www.dropbox.com/
# git/svn: I used to deploy a local version control server, since public
server is not so reliable.
Public server like http://opensvn.csie.org, is not stable.
Google code/git hub force me to share my privacy with the
public.
Regards,
Denny
On 4/26/10, Matt Price <moptop99@gmail.com> wrote:
>
> after cultivating my abbrev_defs file for months i seem to have
> accidentqally overwritten it with a blank one -- it's heartbreaking!
>
> so, having learned the importance of backups, or in this case maybe
> version control, i'm wondering whether anyone out there has a nice
> long abbrev_defs file with their commonly-mistyped English-language
> words -- or if you know a place on the web i can find one. for
> instance, notice that i'm typing 'i' in lowercase -- because i'm used
> to having abbrev-mode correct it for me! anyway, if anyone cal help
> i'd sure appreciate it. thanks much,
>
>
> matt
>
>
>
--
Thanks & Regards
Denny Zhang
[-- Attachment #2: Type: text/html, Size: 1789 bytes --]
next prev parent reply other threads:[~2010-04-26 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 2:58 lost my abbrev-defs file Matt Price
2010-04-26 5:28 ` filebat Mark [this message]
2010-04-26 12:00 ` Andreas Röhler
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=r2zb93cb5f31004252228m2caf06c7y4a966c773353898d@mail.gmail.com \
--to=filebat.mark@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moptop99@gmail.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.
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).