Mail Archives: djgpp/1999/02/14/12:23:06
On Sun, 14 Feb 1999, Daniel Barker wrote:
> I mention another small display-related problem, in case it's relevant.
> EMACS runs in a large box and shrinks it back on exit, using settings from
> the example _emacs:
Yes, this is probably related to the bug. Since you obviously use
fragments from _emacs.xmpl, which is derived from my own _emacs file, my
setup is almost identical to yours in this aspect.
> Run from a command prompt, on exit, EMACS restores the screen size to
> something slightly different from what it was. The number of columns and
> rows seems the same, but the font is a more "squashed up", less readable
> one.
I think this is the effect of the bug, not its cause (i.e., the Windows
screen redirector, which intercepts screen writes by DOS programs and
updates the window of the appropriate DOS box, is already screwed up when
it draws those squashed characters).
> I have associated EMACS with various file types, e.g., .txt, .mft.
> Double-clicking on a few of these leads to many copies of EMACS loaded at
> once, since each new file is given its own copy of EMACS.
On Unix, there's a program called emacsclient which should be associated
with those files. When you click on such a file, the client sends a
message to Emacs (which already runs), and the latter loads the file.
Thus, you avoid several Emacsen.
But this doesn't work in the DJGPP port, because it requires the sockets
interface (to send the message).
So what I do is to avoid associating files with Emacs, and instead I
simply visit them whenever I need to edit them.
> Also, I might use EMACS to
> briefly edit some file from a command prompt, even when it's running
> already elsewhere.
If you need to edit a file without disrupting your Emacs windows'
configuration, open a new frame for the file (with `C-x 5 f filename RET').
This allows you later to return to the previous configuration with
`C-x 5 o'.
- Raw text -