🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.emacs
Article #9802

Problems saving files and exiting

#9802
From: Andrew F. Hampe
Date: Sun, 23 Feb 1992 10:53
27 lines
1697 bytes
Several of our users have repeatedly run into
problems trying to use emacs on several of our
platforms, using various telecommunication means
to these systems.

It appears that the traditional ^X^S rather than
saving the edited file, simple suspends the process,
requiring a ^Q be sent.

Is there some graceful means of REBINDING it all
so that some simpler sequence, that is less likely
to suspend the current shell, can be put together.

I know that the ^X^W will give the users the same
utility as vi's ':w! <fileName>' but I think that
our users are looking for something on the order
of vi's ':w'.

Any assistance you can offer in this will be appreciated.

ciao
drieux

{I have included alt.religion.emacs in the subject line
because I am aware that some devotee's of emacs are found there.
This is NOT a call to a flamefest.}
Technical Details
Message-ID: <1992Feb23.105339.16223@nas.nasa.gov>
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!wilbur!hampe

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 102b9a,63dabd5539bb3d45,start
X-Google-Attributes: gid102b9a,public
X-Google-Thread: ff485,63dabd5539bb3d45,start
X-Google-Attributes: gidff485,public
X-Google-Thread: 104011,63dabd5539bb3d45,start
X-Google-Attributes: gid104011,public
X-Google-Thread: 10e6b9,63dabd5539bb3d45,start
X-Google-Attributes: gid10e6b9,public
X-Google-ArrivalTime: 1992-02-23 03:23:55 PST
Newsgroups: comp.emacs,gnu.emacs,gnu.emacs.gnews,alt.religion.emacs
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!wilbur!hampe
From: hampe@wilbur.nas.nasa.gov (Andrew F. Hampe)
Subject: Problems saving files and exiting
Sender: news@nas.nasa.gov
Organization: OnlyWhereRequiredByLaw
Date: Sun, 23 Feb 92 10:53:39 GMT
Message-ID: <1992Feb23.105339.16223@nas.nasa.gov>
Lines: 31