t above will redefine the "ä" key as expected.
Since I am planning to use Debian on lots of machines, I would strongly
prefer if there was some workaround for the emacs21 debian package
instead of using a self-made emacs on all machines.
Unfortunately, I can't figure out, which mo
This problem makes Emacs very difficult to use without remapping the keyboard.
? Emacs shouldn't care about which Alt key you use
Regards,
Peter Daum
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I am trying to get apt-proxy to work on a test machine running lenny.
Because hardly anything worked as expected, I stripped the configuration
down more and more.but it seems that nothing involving more than 1 backend
works. Here the scenario:
server(lenny) has the following apt-proxy backends:
Celejar wrote:
On Fri, 25 Jul 2008 20:14:54 +0200
Gilles Mocellin <[EMAIL PROTECTED]> wrote:
Le Friday 25 July 2008 18:34:17 Peter Daum, vous avez écrit :
I am trying to get apt-proxy to work on a test machine running lenny.
[...]
Generally, apt-proxy doesn't really look overly
certainly not the most critical problem, but at least on my system (mainly Etch,
I also tried the fortune package from Lenny) doesn't work. when I trace it, I
can see that it reads a bunch of fortue data files but that is obviously just
for its own pleasure - it just silently exits w/o any error.
Mark Allums wrote:
Peter Daum wrote:
certainly not the most critical problem, but at least on my system
(mainly Etch,
I also tried the fortune package from Lenny) doesn't work. when I
trace it, I
can see that it reads a bunch of fortue data files but that is
obviously just
for it
s. keeling wrote:
Peter Daum <[EMAIL PROTECTED]>:
# dpkg -l fortune*|grep ii
ii fortune-mod1.99.1-3.1 provides fortune cookies on demand
ii fortunes 1.99.1-3.1 Data files containing fortune cookies
ii fortunes-min 1.99.1-3.1 Data files containing fortune c
Hi,
For a long time, I always used traditional "hand-made" kernels, so
whenever I needed it (compiling modules from external sources, changing
something in the kernel, ...), I naturally had the source tree and
configuration matching the currently running kernel lying under
"/usr/src/linux". Recen
as I meanwhile could figure out, compiling "linux-source-xxx" failed
because of a mismatch in the gcc versions (gcc 4.3 is installed
as the default C compiler, but the binary kernel packages have been
compiled using gcc 4.1). I still would like to know, what is the
"recommended" way to use the ker
9 matches
Mail list logo
