Re: xterm-debian terminfo entry

1998-06-24 Thread Alexander E. Apke
On Wed, 24 Jun 1998, LeRoy D. Cressy wrote:

> Alexander E. Apke wrote:
> > 
> > 
> > I did not want this to be set in the terminfo entry, but rather
> > added as the default configuration to debian's xterm.  My reasoning is
> > that since the terminfo entry has changed, why can't other configuration
> > settings.  I remember there was a complaint that the debian xterm was
> > straying away from the standard, and that is why the default colors were
> > switched back to black on white from white on black.
> 
> Please, don't go changing the local setup of the users without first
> asking permission to change.  I for one did not like the surprise change
> in the past.  Let's try to keep all surprises down to a minimum.
> 

Well, I guess the original change was to close a very
longstanding bug report.  That was hamm when it was unstable, so
normal users should not have encountered that change.

I propose xbase allowing people to choose between black or white
background during postinst or maybe in some kind of xbaseconfig script.

I know the plan for X is to break up xbase into many smaller
pieces, so the configuration option could be available in the future xterm
package.

Alex



--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: xterm-debian terminfo entry

1998-06-24 Thread Alexander E. Apke
On Wed, 24 Jun 1998, Brian Mays wrote:

> 
> This does not need to be done with at terminfo entry.  Use the following X
> resources (in either $HOME/.Xresources or /etc/X11/Xresources for
> everybody):
> 
>   XTerm*background: black
>   XTerm*foreground: gray90
> 
> By the way, this also will cause rxvt windows to use reverse video.
> 

I did not want this to be set in the terminfo entry, but rather
added as the default configuration to debian's xterm.  My reasoning is
that since the terminfo entry has changed, why can't other configuration
settings.  I remember there was a complaint that the debian xterm was
straying away from the standard, and that is why the default colors were
switched back to black on white from white on black.


Alex



--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



xterm-debian terminfo entry

1998-06-23 Thread Alexander E. Apke
Now that debian is going to be using a nonstandard terminfo entry
for xterms, can the default colors be setup like a normal linux console,
black background with white foreground.

I liked this when the xterm was setup this way a while back.  I
believe the reason for switching back to white background was for
compatibility sake.  Since xterm-debian is the standard terminfo entry
for debian, a black background would also be nice.

The black background is much more pleasing to the eye, especially 
with colors enabled.


Alex


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: BS in rxvt+ncurses

1997-12-08 Thread Alexander E. Apke

> Here are a few related pros and cons.
> 
> <--- == BS, but we must decide on one or the other as the installation 
> default.
> 
> <--- == BS sounds right.  IMHO this is just silly.
> 
> <--- == DEL is different from DOS.  This to is just silly
> 
> <--- == DEL gives us an extra usable key on the main keyboard, since it 
> differentiates between <--- and ^H
> 
> <--- == DEL is standard in Linux-land at the moment (very strong argument for 
> keeping it that way IMHO)
> 
> <--- == BS allows the uninitiated easier use from DOS/Windows telnet's and 
> the 
> like (this needs a HOWTO to explain how to do the configuration, but is 
> probably the strongest argument for the BS setting)


I think there is another reason for choosing <--- == BS, for
internationalization.  I believe it requires <--- == BS, though I am not
entirely sure.  This may be the reason for the push for <--- == BS, even
though debian developers seem to accept  <--- == DEL. 


> In conclusion, I'd say <--- == DEL gets to be the default setting on three 
> grounds:
> 
>  1) Inertia
>  2) Emacs (more inertia and extra functionality)
>  3) Ease of reversing the decision by local admins.
> 
> We need to make point 3 a reality of course ;-)

I agree, but if feel the opposite <--- == BS should be default
because most linux users come from the dos world, and the keys on a linux
terminal/xterm should act the same as in dos.  Emacs users know more about
unix and therfore should know how to change stty erase

But definatly #3 should be followed.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: "purity" package

1997-12-01 Thread Alexander E. Apke
Why do we need to take out the offensive part of the package when
we already have an example of how to package offensive material.  The
fortune and fortune-mod package asks during installation if the offensive
material should be removed.

Why can't we just follow the policy set forward by fortune.


Alex


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Uploaded ppp 2.2.0f-26 (source i386) to master

1997-06-23 Thread Alexander E. Apke
I have been running the 2.3b3 version from experimental.  I have
had a few problem with it, assuming those problems were a result of it
being a beta version.  I think the only reason 2.3b3 is in experimental
was because it was a beta version.  Now that the final release is out, it
might be a good idea to move to the newer one, since it has dial on demand
support built in.  It also may have fixes for those ipx problem some
people were just complaining about.

My email was just to inform you that the new upstream version was
available.



Alex



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Uploaded ppp 2.2.0f-26 (source i386) to master

1997-06-23 Thread Alexander E. Apke
I was just wondering why we havn't upgraded to the new upstream
version 2.3.0, which has been out since may 22.  I would figure it whould
have quite a few fixes for some of the problems in 2.2.0.

Thanks


Alex




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .