sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
* Re: sam-9libs vs. Linux (RH 6.0)
@ 2000-03-28 18:15 Jim Crigler
  2000-03-28 18:28 ` James A. Robinson
  0 siblings, 1 reply; 7+ messages in thread
From: Jim Crigler @ 2000-03-28 18:15 UTC (permalink / raw)
  To: jim.robinson; +Cc: sam-fans

--- "Jim Robinson" <jim.robinson@stanford.edu> wrote:
> > Hmmm ... I asked this on comp.editors a couple of
> weeks ago, and was
> > pointed here as a place to subscribe for real sam
> help.  Under RedHat
> > 6.0 I can run sam -d fine, but when I attempt to
> start the "gui" version,
> > samterm shows up and then disappears.  The sam
> process then dies with a
> > "broken pipe" message.
> 
> I think I responded to your post in Usenet, but in
> case
> you didn't see it: check your color depth. I found
> that
> samterm had problems with (I think) 24 bit depth.
> 
> I normally use 16, and that works fine. I think 32
> should also work.  Try running 'xwininfo' and
> clicking
> on the root window to see what depth it is running
> at.

16-bit X works, thanks.  Neither 24 nor 32 works,
however.  Is this likely to be a libXg problem or
something in samterm per se?
-- 
Another Jim

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: sam-9libs vs. Linux (RH 6.0)
  2000-03-28 18:15 sam-9libs vs. Linux (RH 6.0) Jim Crigler
@ 2000-03-28 18:28 ` James A. Robinson
  2000-03-29  0:07   ` Daniel Neri
  2000-03-29  5:10   ` Scott Schwartz
  0 siblings, 2 replies; 7+ messages in thread
From: James A. Robinson @ 2000-03-28 18:28 UTC (permalink / raw)
  To: Jim Crigler; +Cc: sam-fans

> 16-bit X works, thanks.  Neither 24 nor 32 works,
> however.  Is this likely to be a libXg problem or
> something in samterm per se?

I seem to recall it was a libXg problem. Someone explained that part of
the code expects the depth to be have some properties that don't apply
to 24bit depth (or, I guess, 32bit). I'm sorry that I don't remember
the details.

Jim


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: sam-9libs vs. Linux (RH 6.0)
  2000-03-28 18:28 ` James A. Robinson
@ 2000-03-29  0:07   ` Daniel Neri
  2000-03-29  5:10   ` Scott Schwartz
  1 sibling, 0 replies; 7+ messages in thread
From: Daniel Neri @ 2000-03-29  0:07 UTC (permalink / raw)
  To: jim.robinson; +Cc: Jim Crigler, sam-fans

"James A. Robinson" <jim.robinson@stanford.edu> writes:

> I seem to recall it was a libXg problem. Someone explained that part of
> the code expects the depth to be have some properties that don't apply
> to 24bit depth (or, I guess, 32bit). I'm sorry that I don't remember
> the details.

FWIW, sam(term) works fine for me at 24bit depth (running on
OpenBSD/i386 and XFree86 3.3.5). Though this is "plain sam", not based
on 9libs.


Best wishes,
/Daniel

-- 
Daniel Neri
dne@mayonnaise.net


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: sam-9libs vs. Linux (RH 6.0)
  2000-03-28 18:28 ` James A. Robinson
  2000-03-29  0:07   ` Daniel Neri
@ 2000-03-29  5:10   ` Scott Schwartz
  1 sibling, 0 replies; 7+ messages in thread
From: Scott Schwartz @ 2000-03-29  5:10 UTC (permalink / raw)
  To: sam-fans

| I seem to recall it was a libXg problem. Someone explained that part of
| the code expects the depth to be have some properties that don't apply
| to 24bit depth (or, I guess, 32bit). I'm sorry that I don't remember
| the details.

Yes, exactly.  The bug was, libXg only does power-of-two depths, so 24
bits doesn't work.  Annoyingly, most X servers don't let you ask for
more than one depth visual, which would be the obvious workaround for
something like sam.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: sam-9libs vs. Linux (RH 6.0)
@ 2000-03-29  4:12 Jim Crigler
  0 siblings, 0 replies; 7+ messages in thread
From: Jim Crigler @ 2000-03-29  4:12 UTC (permalink / raw)
  To: Daniel Neri, jim.robinson; +Cc: sam-fans

> "James A. Robinson" <jim.robinson@stanford.edu>
> writes:
> 
> > I seem to recall it was a libXg problem. Someone
> explained that part of
> > the code expects the depth to be have some
> properties that don't apply
> > to 24bit depth (or, I guess, 32bit). I'm sorry
> that I don't remember
> > the details.
> 
> FWIW, sam(term) works fine for me at 24bit depth
> (running on
> OpenBSD/i386 and XFree86 3.3.5). Though this is
> "plain sam", not based
> on 9libs.

Hmm ... I compiled sam-9libs at the same time as
wily-9libs,
and wily seems to have no problem (modulo not getting
caps lock when
it's pressed under wily).
-- 
Jim Crigler

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: sam-9libs vs. Linux (RH 6.0)
  2000-03-27 13:52 Jim Crigler
@ 2000-03-27 20:54 ` James A. Robinson
  0 siblings, 0 replies; 7+ messages in thread
From: James A. Robinson @ 2000-03-27 20:54 UTC (permalink / raw)
  To: Jim Crigler; +Cc: sam-fans

> Hmmm ... I asked this on comp.editors a couple of weeks ago, and was
> pointed here as a place to subscribe for real sam help.  Under RedHat
> 6.0 I can run sam -d fine, but when I attempt to start the "gui" version,
> samterm shows up and then disappears.  The sam process then dies with a
> "broken pipe" message.

I think I responded to your post in Usenet, but in case
you didn't see it: check your color depth. I found that
samterm had problems with (I think) 24 bit depth.

I normally use 16, and that works fine. I think 32
should also work.  Try running 'xwininfo' and clicking
on the root window to see what depth it is running at.


Jim


^ permalink raw reply	[flat|nested] 7+ messages in thread

* sam-9libs vs. Linux (RH 6.0)
@ 2000-03-27 13:52 Jim Crigler
  2000-03-27 20:54 ` James A. Robinson
  0 siblings, 1 reply; 7+ messages in thread
From: Jim Crigler @ 2000-03-27 13:52 UTC (permalink / raw)
  To: sam-fans

Hmmm ... I asked this on comp.editors a couple of
weeks
ago, and was pointed here as a place to subscribe for
real sam help.  Under RedHat 6.0 I can run sam -d
fine,
but when I attempt to start the "gui" version, samterm
shows up and then disappears.  The sam process then
dies with a "broken pipe" message.

Where can I go from here?

BTW, sam works on Solaris (at work) with no problems
at all.
-- 
Jim Crigler

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2000-04-03 22:34 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-03-28 18:15 sam-9libs vs. Linux (RH 6.0) Jim Crigler
2000-03-28 18:28 ` James A. Robinson
2000-03-29  0:07   ` Daniel Neri
2000-03-29  5:10   ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2000-03-29  4:12 Jim Crigler
2000-03-27 13:52 Jim Crigler
2000-03-27 20:54 ` James A. Robinson

sam-fans - fans of the sam editor

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/sam-fans

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 sam-fans sam-fans/ http://inbox.vuxu.org/sam-fans \
		sam-fans@hawkwind.utcs.toronto.edu
	public-inbox-index sam-fans

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.sam-fans


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git