Peter S Galbraith <[EMAIL PROTECTED]> wrote:
> (It seemed silly to add a "lisp" directory unless other packages start
> doing so as well, so I kept the old directory.)
[EMAIL PROTECTED]:554]$ ls /usr/share/emacs/site-lisp/gnus
aclocal.m4 config.status* configure* configure.in lisp/
R
Bill Wohler <[EMAIL PROTECTED]> writes:
> Just out of curiosity, what's the difference between /usr/share/icons
> and /usr/share/pixmaps? I couldn't find anything in either the FHS or
> Debian policy docs.
/usr/share/pixmaps is the traditional location, /usr/share/icons is a
new fd.o-mandated dir
Peter S Galbraith <[EMAIL PROTECTED]> writes:
> I've got lots in /usr/share/picons and elsewhere in app directories on
> my system:
> $ locate .xpm | grep ^/usr/share/pixmaps | wc
> 285 285 10372
> $ locate .xpm | grep -v /usr/share/pixmaps | grep ^/usr | wc
>30793079 163776
>
Bill Wohler <[EMAIL PROTECTED]> wrote:
> Another reason for putting the images directly in etc/images is that it
> simplifies the Debian package configuration. Currently, Peter adds the
> etc/images/mh-e directory to the load-path for Emacs 21 and
> image-load-path (new) in Emacs 22. If the images
Peter S Galbraith <[EMAIL PROTECTED]> wrote:
> Romain Francoise <[EMAIL PROTECTED]> wrote:
>
> > Peter Galbraith <[EMAIL PROTECTED]> writes:
> >
> > > Secondly, the icon images have been moved out of the elisp directory in
> > > CVS Emacs and into
> > >
> > > /usr/share/emacs/VERSION/etc/image
Romain Francoise <[EMAIL PROTECTED]> wrote:
> Peter S Galbraith <[EMAIL PROTECTED]> writes:
>
> > I was wondering why the gnus package did that. I hate symlink farms,
> > but if that's policy...
>
> Well, it's not really policy, the FHS doesn't mention anything about
> /usr/share/pixmaps. I th
Peter S Galbraith <[EMAIL PROTECTED]> writes:
> I was wondering why the gnus package did that. I hate symlink farms,
> but if that's policy...
Well, it's not really policy, the FHS doesn't mention anything about
/usr/share/pixmaps. I think it's just common practice, and it makes
sense. :-)
--
[I should have CC'ed the original message to the MH-E list as well.
I'm doing so now.]
Romain Francoise <[EMAIL PROTECTED]> wrote:
> Peter Galbraith <[EMAIL PROTECTED]> writes:
>
> > MH-E (packaged as mh-e in Debian) has moved it's CVS repository to Emacs
> > itself. Therefore, I should probab
Peter Galbraith <[EMAIL PROTECTED]> writes:
> MH-E (packaged as mh-e in Debian) has moved it's CVS repository to Emacs
> itself. Therefore, I should probably skip package setup for the
> emacs-snapshot flavour. Agreed?
Yes please. (I'll bounce MH-E bug reports to the list anyway.)
> Would peo
Hi all,
MH-E (packaged as mh-e in Debian) has moved it's CVS repository to Emacs
itself. Therefore, I should probably skip package setup for the
emacs-snapshot flavour. Agreed?
--
Secondly, the icon images have been moved out of the elisp directory in
CVS Emacs and into
/usr/share/emacs/VERS
"Christophe Prud'homme" <[EMAIL PROTECTED]> writes:
> I had problems in the past with svn support in emacs-snapshot which
> did allow me to really use emacs-snapshot (well I must admit that I
> didn't really try to fix this).
Not much has changed on that front recently. It must have been caused
Quoting Christophe Prud'homme <[EMAIL PROTECTED]>:
> Hi there,
>
> Just a few words about my experience with emacs-snapshot. Since
> emacs-snapshot
> has been in unstable, I have been testing once in a while. I had problems in
> the past with svn support in emacs-snapshot which did allow me to rea
Hi there,
Just a few words about my experience with emacs-snapshot. Since emacs-snapshot
has been in unstable, I have been testing once in a while. I had problems in
the past with svn support in emacs-snapshot which did allow me to really use
emacs-snapshot (well I must admit that I didn't real
13 matches
Mail list logo
