Re: mozilla-firefox-locale package with all language translations
Hi, On Thu, Nov 11, 2004 at 06:47:15AM +0100, Cesar Martinez Izquierdo wrote: > > The "rules" file includes an "wget" rule that can download the available XPI > files with the translations. > After download new XPI files, if you regenerate the package then you get all > the required files for these new XPIs. This sounds like a very useful package! But why include all translations in the package itself? It should be possible to create an installer package that doesn't include any translations, but instead downloads the translations you selected after installation. Something like the msttcorefonts package does. It would be nice to have a similar package for installing extensions, too. Just a thought. Best regards, Wouter
Re: blue on black is unreadable
> Oh crap, you're right. I wasn't thinking on that one. Oh well, I guess > somebody will have to find good colour combinations for every colour > package. I can do that. Black on white. Proven to work perfectly for centuries. Or do you only read books with white letters on a black background, or all sorts of colors for differently styled text??? > > > Is there a reason why /etc/X11/Xresources/xterm defaults to black on white Is there any reason not to? But a more interesting question is the following: Is there a reason why xterm defaults to color xterm? In slink it does, on potato it's changed all of a sudden. Which is probably the reason I started this thread by filing a bug report against mutt's default colors. (see http://duckman.blub.net/~wouter/muttdefaults.png) > I'm going to go out on a limb and say that not many people actually like > "black" on "white", or vice versa. Well, I do, as you know by now :) > Maybe the default should be > fg: black, bg: blanchedAlmond which works the same as black on white for > configuration of colours in programs, but which doesn't strain the eyes. NO!!! Why does debian have to be different than the rest of the world in everything? Why do I get colors when I set TERM=xterm? there was already xterm-color and xterm-debian which could do colors. Right now, I have to set my TERM to xterm-mono on potato to avoid fruitsalads in a handful of programs I use very often (Mutt, dselect, vim). That is very annoying, because it results in broken terminal settings when I login to *any* other system. Maybe I'm the only one who hates colors in xterms, but still. It should be possible to use xterms without colors in a normal way, and right now it isn't. Please leave *personal* configuration to the *user*, and leave the system configuration to some reasonable, _very_ conservative defaults. Wouter. -- Wat voor een paperclip geldt, geldt in wezen ook voor een server. - Compaq over de nieuwste ProLiant servers
Re: blue on black is unreadable
On Sun, Mar 26, 2000 at 10:11:57AM +1000, Anthony Towns wrote: > On Sun, Mar 26, 2000 at 12:54:39AM +0100, Wouter Hanegraaff wrote: > > Why does debian have to be different than the rest of the world in > > everything? Why do I get colors when I set TERM=xterm? there was already > > xterm-color and xterm-debian which could do colors. > > Other Linux distributions tend to default to a colour xterm, I thought. I thought slackware defaults to a non color xterm, and solaris too. And debian slink too, which is my main problem: Why is this setting changed between slink and potato?? > So why don't you just change your local settings to make xterm be mono? > Ummm. `XTerm*ColorMode: no' seems like it'd do what you want. That seems to work just fine. I wish I was aware of that resource a bit earlier... Wouter
Re: trouble with portmap on diskless machines
On Thu, Aug 31, 2000 at 11:29:06AM +0530, [EMAIL PROTECTED] wrote: > NIS doesn't work on the diskless machines. After some looking around, > I figured that it was the portmapper that really wasn't working. > It shows up in the ps listing, and there are no errors reported during > bootup for portmap. > > But rpcinfo -p localhost says 'RPC: Remote System error - Connection refused' > and ypbind says 'Neigbour table overflow'. That may mean something's wrong with the loopback interface. Does "ifconfig lo up" help anything? Wouter
Bug#45417: general: Lines referring to package remain in /etc/suid.conf after purging
Package: general Version: N/A example: after purging emacs19, the following occurs: 3 [EMAIL PROTECTED] ~ 13:11 # cat /etc/suid.conf | grep emacs emacs /usr/lib/emacs/19.34/i386-debian-linux/movemail root mail 2755 4 [EMAIL PROTECTED] ~ 13:11 # dpkg --purge emacs19 dpkg - warning: ignoring request to remove emacs19 which isn't installed. I think this is a bug. Wouter - System Information Debian Release: 2.1 Kernel Version: Linux kenrsrvr 2.0.36 #3 Wed Jun 2 09:15:52 CEST 1999 i586 unknown
