Your message dated Wed, 27 Jun 2018 21:44:41 -0300
with message-id <87efgrwxhi@tethera.net>
and subject line bug not found with emacs25, org 9.11
has caused the Debian Bug report #363263,
regarding emacs-goodies-el: Session.el conflicts w/ Org Mode of emacs-snapshot
to be marked as done.
Hi,
>> Looks good -- though we'll have to ponder how we want to handle epochs
>> (now that the unversioned package needs to add one). Sean said that
>> there was a DEP suggesting they be included in versions via "%",
>> e.g. 1%20180414-1+git836dce6.
>>
>> I'm not sure what I think about that yet
Hello,
On Sun, May 27 2018, Rob Browning wrote:
> Looks good -- though we'll have to ponder how we want to handle epochs
> (now that the unversioned package needs to add one). Sean said that
> there was a DEP suggesting they be included in versions via "%",
> e.g. 1%20180414-1+git836dce6.
>
> I'
David Bremner writes:
> As far as I know checking is a manual process with the stable emacs
> uploads. But there are many fewer such uploads.
Right. At the moment, I don't have any package-level automated testing.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9
arding the current packaging process.]
Arnaud Fontaine writes:
> I have almost finished preparing emacs-snapshot[0] and as I said to Rob,
> my plan is to keep emacs-snapshot package as close as possible to
> emacsXY package. I know that you've been working on unversioning emacs
Hello,
On Wed, May 23 2018, Arnaud Fontaine wrote:
> Anyhow, emacs-snapshot will only be available in sid/experimental
+1
> But I get your point and indeed there need to be a plan to check
> before each upload of emacs-snapshot whether it breaks add-ons. A
> shell script installin
Dima Kogan writes:
> Arnaud Fontaine writes:
>
>>>> I have almost finished preparing emacs-snapshot[0] and as I said to
>>>> Rob, my plan is to keep emacs-snapshot package as close as possible
>>>> to emacsXY package. I know that you've been
Arnaud Fontaine writes:
>>> I have almost finished preparing emacs-snapshot[0] and as I said to
>>> Rob, my plan is to keep emacs-snapshot package as close as possible
>>> to emacsXY package. I know that you've been working on unversioning
>>> em
Hi,
>> I have almost finished preparing emacs-snapshot[0] and as I said to
>> Rob, my plan is to keep emacs-snapshot package as close as possible
>> to emacsXY package. I know that you've been working on unversioning
>> emacs package (BTW Where is that repos
Arnaud Fontaine writes:
> [Resending this email to debian-emacsen@ as per Rob's request]
>
> Hi,
>
> I have almost finished preparing emacs-snapshot[0] and as I said to Rob,
> my plan is to keep emacs-snapshot package as close as possible to
> emacsXY package
[Resending this email to debian-emacsen@ as per Rob's request]
Hi,
I have almost finished preparing emacs-snapshot[0] and as I said to Rob,
my plan is to keep emacs-snapshot package as close as possible to
emacsXY package. I know that you've been working on unversioning ema
jida...@jidanni.org at "Sun, 13 Oct 2013 16:40:17 +0800" wrote:
j> Gosh emacs-snapshot is made much more than once a week nowadays,
j> $ zgrep -- -- /usr/share/doc/emacs-snapshot/changelog.Debian.gz|head -n 22
j> -- Julien Danjou Sun, 13 Oct 2013 04:26:44
+0200
..
j
Gosh emacs-snapshot is made much more than once a week nowadays,
$ zgrep -- -- /usr/share/doc/emacs-snapshot/changelog.Debian.gz|head -n 22
-- Julien Danjou Sun, 13 Oct 2013 04:26:44
+0200
-- Julien Danjou Sat, 12 Oct 2013 04:26:14
+0200
-- Julien Danjou Thu, 10 Oct 2013 04:26:53
+0200
Axel Beckert writes:
> In toplevel form:
> tex-jp.el:483:1:Error: Invalid read syntax: ". in wrong context"
Recent patches in AUCTeX git:
commit 99841dc2fce69323a3b50471ef42230b6c9613a7
Author: Tassilo Horn
Date: Fri Jun 14 08:07:22 2013 +0200
Fix coding once again.
* tex-jp.el
Hi Julien,
emacs-snapshot 2:20130618-1 fails to upgrade on i386 and amd64 if
auctex is installed:
Install apel for emacs-snapshot
install/apel: already byte-compiled for emacs-snapshot, skipped
Install auctex for emacs-snapshot
auctex/install: Byte-compiling for Emacs flavor emacs-snapshot (log
On Tue, May 14 2013, Romain Francoise wrote:
> Julien Danjou writes:
>
>> Tired of maintaining my own infra, it's time to take a look at what it
>> would take to upload emacs-snapshot¹ packages directly into Debian.
>> I heard there might be some licensing iss
Julien Danjou writes:
> Tired of maintaining my own infra, it's time to take a look at what it
> would take to upload emacs-snapshot¹ packages directly into Debian.
> I heard there might be some licensing issue. What's the status of this
> exactly? How the Emacs maintainers
Hey,
Tired of maintaining my own infra, it's time to take a look at what it
would take to upload emacs-snapshot¹ packages directly into Debian.
I heard there might be some licensing issue. What's the status of this
exactly? How the Emacs maintainers and packages are done?
Hints a
Debian BBDB is getting dangerously behind emacs-snapshot.
Soon it will no longer work with it.
--
To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/
On Sat, Jan 15 2011, jida...@jidanni.org wrote:
> Maybe the new maintainer of emacs-snapshot can take w3m-el-snapshot
> under his wing too...
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607933
I do not use w3m-el so I don't think that would be a good idea. :)
--
Julien
Maybe the new maintainer of emacs-snapshot can take w3m-el-snapshot
under his wing too...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607933
--
To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
I mean there wasn't even a emacs24 non snapshot package to fallback on.
RL> And to Julien Danjou who took over: Merci beaucoup aussi, but an i386
RL> version would be more than welcome :-)
Ah, http://julien.danjou.info/blog/2011.html#Emacs_snapshot_Debian_packages
How could I have (not) missed it
trentb...@gmail.com writes:
> jida...@jidanni.org wrote:
>> > "TWB" == Trent W Buck writes:
>> TWB> $ w3m -dump emacs.orebokech.com
>> TWB> As of January 2011, this site will no longer be updated.
>>
>> TWB> Can anyone tell me *why* that resource is deprecated? I can't find any
>> TWB> expl
jida...@jidanni.org wrote:
> > "TWB" == Trent W Buck writes:
> TWB> $ w3m -dump emacs.orebokech.com
> TWB> As of January 2011, this site will no longer be updated.
>
> TWB> Can anyone tell me *why* that resource is deprecated? I can't find any
> TWB> explanation on this list nor or emacs-dev
> "TWB" == Trent W Buck writes:
TWB> $ w3m -dump emacs.orebokech.com
TWB> As of January 2011, this site will no longer be updated.
TWB> Can anyone tell me *why* that resource is deprecated? I can't find any
TWB> explanation on this list nor or emacs-devel.
Unacceptable. They pulled the rug
$ w3m -dump emacs.orebokech.com
As of January 2011, this site will no longer be updated.
Can anyone tell me *why* that resource is deprecated? I can't find any
explanation on this list nor or emacs-devel.
--
To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org
with a subject of "un
On 2009-08-15 17:57 +0200, Simon Josefsson wrote:
> I was thinking more in terms of compilation options or different library
> dependencies. I don't need any elisp code beyond what's in 23.1, or so
> I believe, so I'm wondering if there is anything in it for me to kee
Manoj Srivastava writes:
> Hi,
>
> On Sat, Aug 15 2009, Simon Josefsson wrote:
>
>> So now that emacs 23.1 has been released, and uploaded, is there any
>> significant difference between the official emacs23-gtk package and the
>> emacs-snapshot packages?
>
>
Hi,
On Sat, Aug 15 2009, Simon Josefsson wrote:
> So now that emacs 23.1 has been released, and uploaded, is there any
> significant difference between the official emacs23-gtk package and the
> emacs-snapshot packages?
I was under the impression that emacs-snapshot follows t
So now that emacs 23.1 has been released, and uploaded, is there any
significant difference between the official emacs23-gtk package and the
emacs-snapshot packages?
/Simon
--
To UNSUBSCRIBE, email to debian-emacsen-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
cs-install ${FLAVOR}
The former removes all .elc files for ${FLAVOR} that have been
generated from separately distributed Elisp packages and the latter
recompiles them with the new version.
>> I see two reasons for calling the packages emacs23-snapshot* as
>> opposed to emacs-snapshot:
&g
who will get
> to keep both pieces if anything breaks). The -snapshot packages
> probably shouldn't become a part of stable releases.
>
> I see two reasons for calling the packages emacs23-snapshot* as
> opposed to emacs-snapshot:
>
> a) There'd be a sane upgrade path on
he packages emacs23-snapshot* as
>> opposed to emacs-snapshot:
>>
>> a) There'd be a sane upgrade path once Emacs 23 is released.
>
> What upgrade path? Do you suggest that emacs23-snapshot should
> provide the emacs23 flavor? Otherwise this does not make sense to
&
bjunctive here: are you aware of the snapshots
available from http://emacs.orebokech.com/?
> I see two reasons for calling the packages emacs23-snapshot* as
> opposed to emacs-snapshot:
>
> a) There'd be a sane upgrade path once Emacs 23 is released.
What upgrade path? Do you
t
packages probably shouldn't become a part of stable releases.
I see two reasons for calling the packages emacs23-snapshot* as
opposed to emacs-snapshot:
a) There'd be a sane upgrade path once Emacs 23 is released.
b) Elisp packages can specify for which package they should be
byte
Brendan Halpin <[EMAIL PROTECTED]> writes:
> If I have further problems is there a suitable forum for
> emacs-snapshot issues? It always helps to have public questions and
> answers.
I don't understand why this isn't a suitable forum...
Even if the emacs-snapshot packa
Brendan Halpin <[EMAIL PROTECTED]> writes:
> If I have further problems is there a suitable forum for
> emacs-snapshot issues?
Unfortunately, no. Perhaps I should set up a Google Group or
something.
--
,''`.
: :' :Romain Francoise <[EMAIL P
Romain Francoise <[EMAIL PROTECTED]> writes:
> Why don't you use the etch backport instead? It should work on
> lenny too (but I haven't tried).
Thanks for the explanation. I'll try the backport.
If I have further problems is there a suitable forum for
emacs-snaps
Hi,
I'm not sure if emacs-snapshot questions are relevant on
debian-emacsen, since the packages are not in Debian anymore. Feel
free to email me privately in case of problems.
Brendan Halpin <[EMAIL PROTECTED]> writes:
> I have two machines running Lenny. One has happily up
I have two machines running Lenny. One has happily upgraded
emacs-snapshot to 23.0.50.1 "(i486-pc-linux-gnu, GTK+ Version
2.10.13, multi-tty) of 2007-09-03 on pacem, modified by Debian".
The other refuses due to a dependency on a more recent libgtk2:
| The following packages
Petteri <[EMAIL PROTECTED]> writes:
> Any chance of getting XFT branch of emacs-snapshot. I have been
> compiling my own from emacs cvs and it seems quite stable (compared to a
> year a go when it segfaulted at least once a day).
FYI, I have been using the following Makefile to b
Romain Francoise kirjoitti su 25. helmikuuta 2007 14:07:12:
> Petteri <[EMAIL PROTECTED]> writes:
>
> > Any chance of getting XFT branch of emacs-snapshot. I have been
> > compiling my own from emacs cvs and it seems quite stable
> > (compared to a year a go when it
Petteri <[EMAIL PROTECTED]> writes:
> Any chance of getting XFT branch of emacs-snapshot. I have been
> compiling my own from emacs cvs and it seems quite stable
> (compared to a year a go when it segfaulted at least once a day).
Yes, it is quite stable now. I think it'll be
Any chance of getting XFT branch of emacs-snapshot. I have been
compiling my own from emacs cvs and it seems quite stable (compared to a
year a go when it segfaulted at least once a day).
Petteri
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
On August 5th 2005 I uploaded the first version of emacs-snapshot to
unstable. One year and 55 uploads later, we're nearing the 400
installations mark[1] in popcon, with the following subflavour
repartition:
GTK: 55.1%
X11: 32.7%
NoX: 18.6%
(Quite a few installations have more tha
[EMAIL PROTECTED] (Thomas Hahn) writes:
>>>Error occurred processing semantic-analyze.el: File error (("Cannot
>>>open load file" "semantic-el"))
>>>Error occurred processing semantic-ast.el: File error (("Cannot open
>>>load file" "semantic-el"))
> Although I do not know how to fix this, I can i
Hello, I have trouble getting semantic configured
for emacs snapshot.
...
Loading /etc/emacs/site-start.d/55doxymacs.el (source)...
Loading /etc/emacs/site-start.d/55ecb.el (source)...
Wrote /usr/share/emacs-snapshot/site-lisp/semantic/document-vars.elc
Wrote /usr/share/emacs-snapshot/site-lisp
Dan Jacobson <[EMAIL PROTECTED]> writes:
> If I installed emacs-snapshot, then should I purge gnus, as
> emacs-snapshot's gnus is newer than gnus package's gnus?
No, Gnus from the gnus package is newer.
--
,''`.
: :' :Romain Francoise &l
If I installed emacs-snapshot, then should I purge gnus, as
emacs-snapshot's gnus is newer than gnus package's gnus?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Romain Francoise <[EMAIL PROTECTED]> writes:
> * I've also been wondering if I should reconsider my 'sid-only' policy
> for emacs-snapshot, I keep getting requests from users to let it
> trickle into testing, and given that the past few months have s
>From my blog:
* In case anyone's interested I maintain an official sarge backport of
my [1 emacs-snapshot packages], available from [2 here]. It's updated
frequently, but not as often as in sid.
Note that quite a few Emacs-related packages in sarge don't ha
Sven Joachim <[EMAIL PROTECTED]> writes:
> I think it would be a good idea to give the subflavors different
> priorities, in the order emacs-snapshot-gtk > emacs-snapshot-x >
> emacs-snapshot-nox, as I guess this order would be preferred by most
> people.
> What
Agustin Martin <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 14, 2006 at 10:32:31PM -0500, Peter S Galbraith wrote:
> > Romain Francoise <[EMAIL PROTECTED]> wrote:
> >
> > > Peter S Galbraith <[EMAIL PROTECTED]> writes:
> > >
> > > >
On Tue, Feb 14, 2006 at 10:32:31PM -0500, Peter S Galbraith wrote:
> Romain Francoise <[EMAIL PROTECTED]> wrote:
>
> > Peter S Galbraith <[EMAIL PROTECTED]> writes:
> >
> > > The load-path of emacs-snapshot includes all the
> > > /usr/share/ema
Romain Francoise <[EMAIL PROTECTED]> wrote:
> Peter S Galbraith <[EMAIL PROTECTED]> writes:
>
> > The load-path of emacs-snapshot includes all the
> > /usr/share/emacs/site-lisp subdirectories.
>
> It doesn't here.
>
> Would you by any cha
Peter S Galbraith <[EMAIL PROTECTED]> writes:
> The load-path of emacs-snapshot includes all the
> /usr/share/emacs/site-lisp subdirectories.
It doesn't here.
Would you by any chance still have emacs20 installed? It shipped a
subdirs.el file in /usr/share/emacs/site-lisp whic
Hi all,
I thought I'd discuss here before reporting a bug. The load-path of
emacs-snapshot includes all the /usr/share/emacs/site-lisp
subdirectories. This has the side effect that Debian packages that
don't want to setup themselves for emacs-snapshot find themselves in the
load-p
Romain Francoise wrote:
Starting with version 20060120-2, it is now possible to install the -x,
-gtk and -nox binary packages concurrently. The new alternative
`emacs-snapshot' determines which package owns the emacs-snapshot
command.
There is currently no preference which binary own
Starting with version 20060120-2, it is now possible to install the -x,
-gtk and -nox binary packages concurrently. The new alternative
`emacs-snapshot' determines which package owns the emacs-snapshot
command.
Note that if you're upgrading from the current emacs-snapshot packages,
Sven Joachim wrote (27 Dec 2005 13:07:24 GMT) :
> On Sat, 24 December, "intrigeri" wrote:
>
>> Hello,
>> I usually backport emacs-snapshot and a few related packages for my
>> own use. There are now in a Debian repository :
>> deb http://intrigeri.boum.org/
On Sat, 24 December, "intrigeri" wrote:
Hello,
I usually backport emacs-snapshot and a few related packages for my
own use. There are now in a Debian repository :
deb http://intrigeri.boum.org/deb sarge main contrib non-free
Nice, but there is an important issue: To comply with th
whazzup!
Hello,
I usually backport emacs-snapshot and a few related packages for my
own use. There are now in a Debian repository :
deb http://intrigeri.boum.org/deb sarge main contrib non-free
Ciao,
--
intrigeri <[EMAIL PROTECTED]>
| gnupg key @ http://intrigeri.boum.org/intrigeri.asc
>>>>> "c" == csj <[EMAIL PROTECTED]> writes:
c> Under emacs-snapshot 20051207-1, I get the following error when
c> opening or creating a *.ly file:
c> File mode specification error: (wrong-type-argument arrayp 0)
I think this problem was fi
Hi,
> > elserv.el
> > elserv-url-decode-string()
> > (push ?\ decoded)
> >
> > is breaking in emacs-snapshot.
> >
> > emacs-snapshot probably wants
> > (push ?\\ decoded)
>
> In emacs21, the following S expressio
[EMAIL PROTECTED] wrote:
Under emacs-snapshot 20051207-1, I get the following error when
opening or creating a *.ly file:
File mode specification error: (wrong-type-argument arrayp 0)
Can somebody else confirm the problem? Lilypond mode appears to
work for my installation of emacs21. Bu I
Under emacs-snapshot 20051207-1, I get the following error when
opening or creating a *.ly file:
File mode specification error: (wrong-type-argument arrayp 0)
Can somebody else confirm the problem? Lilypond mode appears to
work for my installation of emacs21. Bu I haven't reinstalled or
upg
d if not, they are mostly
> useless.
FWIW, the packaging is based on an earlier version of emacs-snapshot,
and I find it integrates quite well with Debian's elisp packages.
However, I don't think it would be a good idea to add the
emacs-multi-tty packages to the Debian archive. This
You ([EMAIL PROTECTED]) wrote:
DB> Everyone is aware of the multi-tty Debian packages linked to
DB> from the aforementioned page, right? (Just making sure.)
I'm not sure are they properly Debianized, and if not, they are mostly
useless.
--
Mikhail Gusarov
ICQ UIN: 111575219
JID: [EMAIL PROT
Henrik Enberg <[EMAIL PROTECTED]> writes:
>> Will it be hard to merge Multi-TTY Emacs branch
>> (http://lorentey.hu/project/emacs.html.en) changes to the
>> emacs-snapshot package?
>
> I wonder if it is wise to deviate from standard Emacs so much.
> It would prob
> From: Mikhail Gusarov <[EMAIL PROTECTED]>
> Date: Wed, 23 Nov 2005 01:25:22 +0600
>
> Will it be hard to merge Multi-TTY Emacs branch
> (http://lorentey.hu/project/emacs.html.en) changes to the
> emacs-snapshot package?
I wonder if it is wise to deviate from standard
Agustin Martin <[EMAIL PROTECTED]> writes:
> emacs20: /usr/share/emacs/site-lisp/subdirs.el !!
Heh, looks like you rediscovered bug #62853. :-)
--
,''`.
: :' :Romain Francoise <[EMAIL PROTECTED]>
`. `' http://people.debian.org/~rfrancoise/
`-
--
On Wed, Nov 23, 2005 at 02:12:19PM +0100, Romain Francoise wrote:
> Agustin Martin <[EMAIL PROTECTED]> writes:
>
> > However emacs-snapshot seems to load ispell and flyspell from
> > dictionaries-common rather than from its byte-compiled files
>
> Are you
Agustin Martin <[EMAIL PROTECTED]> writes:
> However emacs-snapshot seems to load ispell and flyspell from
> dictionaries-common rather than from its byte-compiled files
Are you sure? It doesn't do that here...
ELISP> (locate-library "flyspell")
"/usr
On Wed, Nov 23, 2005 at 12:52:00PM +0100, Agustin Martin wrote:
> and loads dict-common files because they are found first, despite they
> are not byte-compiled and the byte-compiled ones are available for
> emacs-snapshot.
>
> Any hint about the best way to deal with this?
Fo
Hi,
I am looking for help about this,
dictionaries-common currently ships ispell.el and flyspell.el in
/usr/share/emacs/site-lisp/dictionaries-common, and they will be
byte-compiled for any emacs flavour but emacs-snapshot.
dict-common initialization file does nothing for emacs-snapshot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikhail Gusarov <[EMAIL PROTECTED]> writes:
> Will it be hard to merge Multi-TTY Emacs branch
> (http://lorentey.hu/project/emacs.html.en) changes to the
> emacs-snapshot package?
As a side note, I'd be very interested in hav
Will it be hard to merge Multi-TTY Emacs branch
(http://lorentey.hu/project/emacs.html.en) changes to the
emacs-snapshot package?
I've compiled lastest emacs-snapshot with applied diff of Multi-TTY
branch against CVS Emacs (it applied ok with trivial conflicts) and it
seems to work fi
"Aaron S. Hawley" <[EMAIL PROTECTED]> writes:
> What about the other dozen topics under "Emacs snapshot"?
No easy way... it's a known problem of the Emacs info reader.
--
,''`.
: :' :Romain Francoise <[EMAIL PROTECTED]&
On Thu, 10 Nov 2005, Romain Francoise wrote:
> "Aaron S. Hawley" <[EMAIL PROTECTED]> writes:
>
> > I'm wondering if anybody knows of a quick way to get to a particular
> > [Emacs snapshot] manual from the keyboard.
>
> In emacs-snapshot, `C-h r'.
"Aaron S. Hawley" <[EMAIL PROTECTED]> writes:
> I'm wondering if anybody knows of a quick way to get to a particular
> manual from the keyboard.
In emacs-snapshot, `C-h r'.
--
,''`.
: :' :Romain Francoise <[EMAIL PROTECTED]>
I currently have both emacs21 and emacs-snapshot installed. Thanks for
those, especially the Emacs CVS snapshot package.
I noticed that `/usr/share/info/dir' has an "Emacs" and an "Emacs
Snapshot" heading for access to the documentation for both of the
respective pa
[ Lundi 17 Octobre 2005 14:23 ]
| "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
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. :-)
--
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.)
Ok then.
Feel free to reassign MH-E bugs to the mh-e package anyway. I'm also
a member of
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 t
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/
"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
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-s
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&#
Hi Sven,
Sven Joachim <[EMAIL PROTECTED]> writes:
> The packages emacs-snapshot-{el,common,bin-common} replace old
> versions of emacs21 (<< 21.2-4). Surely there is no need to do this,
> is it?
Certainly not.
> It seems to be a remnant of the later emacs21 packa
The packages emacs-snapshot-{el,common,bin-common} replace old versions of
emacs21
(<< 21.2-4). Surely there is no need to do this, is it? It seems to be a
remnant
of the later emacs21 packaging, which changed in version 21.2-4. I think you
can
safely remove the lines which state
Re
Rob Browning <[EMAIL PROTECTED]> wrote:
> I'd like to figure out what needs fixing and fix it, but I want to be
> careful because some of the emacsen-common stuff is trickier than I
> often think at first glance.
>
> > I wouldn't have a problem with that, it's your choice. Perhaps there is
> > a
Rob Browning <[EMAIL PROTECTED]> wrote:
> Peter S Galbraith <[EMAIL PROTECTED]> writes:
>
> > How likely it is that we can get emacsen-common fixed? That package has
> > seen a single upload since `oldstable' (woody?)
>
> Hmm, though there was a long period with no uploads, 1.4.16 was
> uploade
1 - 100 of 253 matches
Mail list logo
