Some questions

Thread View: gnu.epoch.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Michael Sennett Mon, 05 Aug 1991 19:22

#1830

Author: Michael Sennett
Date: Mon, 05 Aug 1991 19:22

34 lines
2099 bytes

I have a few Epoch questions that I've been saving up. We're using Epoch
3.2 on Sun 3s and Sun 4s. 

* I have been using the `set-window-buffer-hook' to keep the X window names in
sync with the buffer currently displayed in the screen.  I haven't had any
problems with this, but a comment in the source calls it "undocumented" and
"dangerous".  Is there a better way to accomplish this without using the
`set-window-buffer-hook' (or rebinding every command that could possibly
change the buffer being displayed in a screen)?

* Has anyone experimented with or even thought about what would be involved in
supporting "cut and paste" for buttons.  That is, allowing a region with
buttons to killed, and then restoring the buttons when it's yanked into 
another location.

* If I make a selection using the mouse, then move the cursor forward a few
positions with C-f, mouse events seem to be blocked until I do a C-n or C-b
to get the cursor out of the selection.  Has anyone else noticed this
behavior?

* Is there anyway to disable the mouse, while I'm prompting the user for
a response in the minibuffer?  Right now, it seems that a mouse click on a
screen makes Epoch forget about the read-string function that is
executing.

* Is there a simple way to setup a screen so that only the buffer
originally passed to create-screen can be displayed in it (with exceptions
for *Help*, etc.) In other words, I want to tie a screen and a buffer
together until the screen is removed.

Any help would be appreciated. Thanks,

-Mike Sennett
sennett@vistatech.com

Re: Some questions

#1838

Author: Alan M. Carroll
Date: Sat, 10 Aug 1991 19:56

44 lines
2762 bytes

In article <1152@sol.UUCP>, sennett@sol.UUCP (Michael Sennett) writes:
> * I have been using the `set-window-buffer-hook' to keep the X window names in
> sync with the buffer currently displayed in the screen.  I haven't had any
> problems with this, but a comment in the source calls it "undocumented" and
> "dangerous".  Is there a better way to accomplish this without using the
> `set-window-buffer-hook'

It's clearly undocumented :-), and it is dangerous. It's easy to
completely hose Epoch using it. Unfortunately, there's no better way
to keep the window title and buffer title coherent.

> * Has anyone experimented with or even thought about what would be involved in
> supporting "cut and paste" for buttons.

Not really. IMHO the key question is what to do with buttons that are
only partially in the cut region.

> * If I make a selection using the mouse, then move the cursor forward a few
> positions with C-f, mouse events seem to be blocked until I do a C-n or C-b
> to get the cursor out of the selection.  Has anyone else noticed this
> behavior?

It's not a mouse event problem, but a display problem. The mouse
events do what they are supposed to, but the display doesn't update. I
thought we'd put a fix in for that in patch 2, but possibly not.

> * Is there anyway to disable the mouse, while I'm prompting the user for
> a response in the minibuffer?

I would recommend using (ignore-event 'motion) (ignore-event 'button)
before and (resume-event 'motion) (resume-event 'button) afterwards.

> * Is there a simple way to setup a screen so that only the buffer
> originally passed to create-screen can be displayed in it (with exceptions
> for *Help*, etc.)

This is difficult. Each buffer has a buffer local variable named
allowed-screens. The default buffer selection won't select a buffer
unless the screen is in the list in that variable.

-- 
Alan M. Carroll          <-- Another casualty of applied metaphysics
Epoch Development Team   
Urbana Il.               "I hate shopping with the reality-impaired" - Susan

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads