🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

3 total messages Started by Stacy Marsella Tue, 28 Jul 1992 00:31
minibuffer title and icon problems
#49
Author: Stacy Marsella
Date: Tue, 28 Jul 1992 00:31
27 lines
1547 bytes
I recently started using epoch 3.2 under X11R5 and noticed a new
behavior for the minibuffer's title. The Minibuffer is now titled
"Minibuffer @ hostname" where hostname is the actually name of
whatever host (console) that I am on. Considering that this version of
epoch was compiled under R4, this would not be too disturbing except
that the change in title name means that the following settings inside
.twmrc or .tvtmwrc no longer work.

      IconManagerDontShow {"Minibuffer"}
 and
      NoTitle {"Minibuffer"}

So I am getting a title on the minibuffer and an icon for it when I
use R5, but this worked fine under R4.  It is not apparent from the
various setup files where things are going amiss, especially since
the problem only occurs if I invoke epoch in .xinitrc prior to
invoking twm or tvtwm.  If I invoke epoch in an xterm after the window
manager has started then it works fine.

Is anyone familiar with this problem?  At the moment it is not a
simple matter to recompile epoch 3.2 or 4.0 under R5 and besides I am
not sure that will solve this problem. Any suggestions would be
appreciated.

Thanks

S. Marsella
Re: minibuffer title and icon problems
#57
Author: Simon Marshall
Date: Wed, 29 Jul 1992 10:00
34 lines
2061 bytes
In article <Jul.27.20.31.06.1992.13218@dartagnan.rutgers.edu> marsella@dartagnan.rutgers.edu (Stacy Marsella) writes:
>I recently started using epoch 3.2 under X11R5 and noticed a new
>behavior for the minibuffer's title. The Minibuffer is now titled
>"Minibuffer @ hostname" where hostname is the actually name of
>whatever host (console) that I am on. Considering that this version of
>epoch was compiled under R4, this would not be too disturbing except
>that the change in title name means that the following settings inside
>.twmrc or .tvtmwrc no longer work.
>
>      IconManagerDontShow {"Minibuffer"}
> and
>      NoTitle {"Minibuffer"}

I may be wrong, but this sounds like the `fault' is with twm, not epoch.  When
we moved to R5 from R4, I noticed that using the Icons{} declaration:

Icons {
	"emacs"		"emacs.xbm"		"tcsh"		"tcsh.xbm"
	"epoch"		"epoch.xbm"		"csh"		"csh.xbm"
}

did not result in those windows with titles *beginning* with "emacs", "tcsh"
etc. using the relevant bitmap as icon (the window names are of the form
"app@hostname").  The change was that R5 twm matches *exactly* with the
specified string, rather than matching the beginning.  (I prefer the R4
behaviour myself.)  The fix, if this is the case, is to hack the twm code, or,
as I ended up doing, listing each possible string of the form "Minibuffer @
hostname" in the declarations.

Have fun.  Simon.
-- 
Simon Marshall, Dept. of Computer Science, University of Hull, Hull HU6 7RX, UK
  "Football isn't about life and death.  It's more important than that." Bill
Email: S.Marshall@Hull.ac.uk    Phone: +44 482 465181    Fax: 466666   Shankley
Re: minibuffer title and icon problems
#72
Author: Stacy Marsella
Date: Thu, 30 Jul 1992 15:51
11 lines
921 bytes
As several people have suggested, twm under R5 matches the entire
string, as opposed to just a prefix, so NoTitle{ Minibuffer } will not work 
when "@ host" is appended to the title. Several people also suggested
the simple solution of adding an epoch.minibuf.class to .Xdefaults for the
minibuffer and then NoTitle on that class in twmrc should work. It
does.

Thanks to everyone for their suggestions and help.

Stacy
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