tag 512784 + confirmed
thanks

I personally use icicles in emacs in a tty, so disabling it altogether
in that case is not an option, but I will work something out...

Cheers,

--Seb

On Fri, Jan 23, 2009 at 05:44:21PM +0000, Toby Speight wrote:
> Package: icicles
> Version: 22.0+20081227-1
> Severity: normal
> 
> After installing icicles, *all* users get the following message when
> starting emacs on console, xterm or telnet session:
> 
> /--------
> | You might NOT want to use Icicles without a windowing system (manager).
> |
> | Consider using `emacsclient' (or `gnuclient').  Icicles makes use of many
> | keys that are unavailable when running Emacs in console mode.  If you do
> | use Icicles in this mode, you will want to rebind those keys - see file
> | `icicles-mode.el'.
> \--------
> 
> or (with --batch):
> 
> /--------
> | *WARNING* - Icicles uses keys that require a windowing system
> \--------
> 
> The package shouldn't be so aggressive simply on Emacs start-up - such
> a message would be fine when enabling icicles-mode, for instance, but
> is just an irritation for the user otherwise.
> 
> As an interim, temporary fix, perhaps the site-start.d file should
> duplicate the
> 
> /--------
> | (or window-system (and (fboundp 'daemonp) (daemonp)))
> \--------
> 
> test in icicles.el to determine whether or not to load it?
> 
> 
> -- System Information:
> Debian Release: 5.0
>   APT prefers testing
>   APT policy: (990, 'testing'), (900, 'stable'), (400, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.26 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages icicles depends on:
> ii  emacs22 [emacsen]             22.2+2-5   The GNU Emacs editor
> 
> icicles recommends no packages.
> 
> icicles suggests no packages.
> 
> -- no debconf information
> 
> 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to