From: storm@cua.dk (Kim F. Storm)
Cc: bob@rattlesnake.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: xfaces.c: error: `ngcs' undeclared
Date: Fri, 04 Feb 2005 16:09:42 +0100 [thread overview]
Message-ID: <m34qgswedl.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <fc339e4a050204052566ca492c@mail.gmail.com> (Miles Bader's message of "Fri, 4 Feb 2005 22:25:07 +0900")
Miles Bader <snogglethorpe@gmail.com> writes:
> On Fri, 04 Feb 2005 10:58:03 +0100, Kim F. Storm <storm@cua.dk> wrote:
>> > Does it disable auto-save mode?
>>
>> No. But still, some work is not always saved (e.g. if you work in a
>> shell buffer, or while composing a mail message).
>
> Mail composition buffers are auto-saved; Gnus also checkpoints its
> state whenever you exit a group. I find the main annoyance is process
> state.
Auto-save doesn't guarantee that everything you wrote is saved...
And you process state gets lost.
Also, one thing which has bitten me more than once is while
debugging something with gdb -- if emacs crashes on you,
your gdb session is lost -- any you may have worked for a long
time to get into an interesting state in your program...
>
> One habit I have adopted since using starting to use the development
> version of Emacs is creating scratch buffers by doing "C-x C-f
> /tmp/foo" rather than just "C-x b foo", which ensures that they're
> autosaved too.
>
> -Miles
> --
> Do not taunt Happy Fun Ball.
>
>
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-02-04 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 13:19 xfaces.c: error: `ngcs' undeclared Robert J. Chassell
2005-02-03 13:46 ` Lute Kamstra
2005-02-03 14:45 ` Lute Kamstra
2005-02-03 15:39 ` Robert J. Chassell
2005-02-03 16:01 ` Kim F. Storm
2005-02-03 16:50 ` Robert J. Chassell
2005-02-03 22:46 ` Miles Bader
2005-02-04 9:58 ` Kim F. Storm
2005-02-04 13:25 ` Miles Bader
2005-02-04 15:09 ` Kim F. Storm [this message]
2005-02-04 16:12 ` Miles Bader
2005-02-04 16:28 ` Romain Francoise
2005-02-05 0:39 ` Miles Bader
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=m34qgswedl.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=miles@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.
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).