🚀 go-pugleaf

>>>>> In article <2omfaj$4d@lastactionhero.rs.itd.umich.edu>,
Jim.Rees@umich.edu writes: Jim.Rees> In article
<TKLD.94Apr15093643@scott.cogsci.ed.ac.uk>, tkld@cogsci.ed.ac.uk (Kevin Davidson) writes: 
Jim> Completions frame says "Click mouse-2 on a completion to select it," but 
Jim> that's a lie.  Mouse 2 pasteslike anywhere else.

tkld> Untrue. Mouse 2 selects a completion.

Jim.Rees> I'll be generous here and assume that what you mean is it
Jim.Rees> works for you.  So the interesting question is why it works
Jim.Rees> for you but not for me.  I haven't really investigated this
Jim.Rees> yet.

  Ouch! Yes, I mean for me.
  Perhaps you have some Epoch resources or elisp still lying about.
Check (or remove) your X resources and start up emacs with the -q flag.

Jim.Rees> I did, and I still get a *scratch* frame when I start emacs.
Jim.Rees> In case it isn't clear, what I want is the equivalent of
Jim.Rees> inhibit-initial-screen-mapping.

  If you mean you want rid of the initial frame that opens while your
.emacs is being read, I want rid of it as well. The default-frame-alist
et. al. only seem to take effect after .emacs has been read. I suppose
this is to guarantee that there's a minibuffer if things go wrong.
From frame.el, it seems that the initial frame gets set up
as a before-init-hook, so there's no way to bypass it from .emacs.

Jim.Rees> I'd like to get normal X behavior.  If the frame has the
Jim.Rees> focus, I should have a reverse video block cursor.  If it
Jim.Rees> doesn't, I should have a box cursor.  I should never have an
Jim.Rees> opaque black cursor, and that's what I get sometimes.  It's
Jim.Rees> not consistent, and I don't know how to reproduce it.

  Works fine for me. Sounds like your window manager getting the focus 
wrong, or perhaps two dark colours both being shown as black on a mono
display.

Jim> better frame placement would be nice.
tkld> Better, how ?
Jim.Rees> Regular frames should never obscure the minibuf frame.  This
Jim.Rees> isn't a killer, just a wishlist item.

  When the frame is created, you mean ? Or at any time ? Isn't this 
a window manager issue ?

Jim.Rees> I want the same thing epoch gives me, whatever that's
Jim.Rees> called.  Dragging mouse 1 should leave point unchanged, set
Jim.Rees> and move the mark, and hilight the region and copy it to the
Jim.Rees> X cut buffer (or whatever they're calling it this week).  I
Jim.Rees> know I can do this, I just haven't figured out how yet.

  This is a secondary selection. M-mouse-1 is what you want.

Jim> gnuclient doesn't return until emacs exits.
tkld> C-x # makes it return as usual.
Jim.Rees> I want it to return when I delete the frame.

 Ah. I don't think there's a delete-frame-hook that could run server-edit.
I found that deleting frames (from the window manager) killed emacs
anyway and C-x 5 0 is an extra key stroke :-) Perhaps it should be the
other way round - the last call to server-edit could call delete-frame
if we're using a window system...

--
|Kevin.Davidson@edinburgh.ac.uk +-+ Centre for Cognitive Science/HCRC,        |
|tkld@cogsci.ed.ac.uk           | | University of Edinburgh,                  |
|+44 31 650 4447         .oOo.  | | 2 Buccleuch Place, EH8 9LW.        .oOo.  |
`-------------------------------' `-------------------------------------------'