#977918 vm: Package vm prevents clean emacs27 start

Package:
vm
Source:
vm
Submitter:
Dirk Eddelbuettel
Date:
2021-01-18 14:06:02 UTC
Severity:
normal
#977918#5
Date:
2020-12-22 21:44:41 UTC
From:
To:
Using the (awesome !!) newer emacs 27.1, I am having issues with package
vm. One issue is that on startup, a message 'Package cl is deprecated' is
shown.  Startup appears to finish in interactive, but does not in daemon mode
which is how I used to use emacs. So the message prevents daemon mode from
working.

Moreover, some googling reveals that 'cl' is indeed deprecated and vm ideally
should move on from it.  An upgrade would be great, but it is not clear how
active upstream still is.

A fix / update to vm would be awesome. It's been my goto mail client since
forever.

Dirk
#977918#10
Date:
2020-12-22 22:12:54 UTC
From:
To:
    Package: vm
    Version: 8.2.0b-6
    Severity: serious

    Using the (awesome !!) newer emacs 27.1, I am having issues with package
    vm. One issue is that on startup, a message 'Package cl is deprecated' is
    shown.  Startup appears to finish in interactive, but does not in daemon mode
    which is how I used to use emacs. So the message prevents daemon mode from
    working.

    Moreover, some googling reveals that 'cl' is indeed deprecated and vm ideally
    should move on from it.  An upgrade would be great, but it is not clear how
    active upstream still is.

    A fix / update to vm would be awesome. It's been my goto mail client since
    forever.

And of course in a minimal container with just emacs27 and vm the issue does
not reproduce. While I have a lot of general programming stuff in .emacs,
there is not that much relative to vm so I am a little ... stumped.

Dirk
#977918#15
Date:
2021-01-18 13:47:34 UTC
From:
To:
Dirk Eddelbuettel writes ("Bug#977918: vm: Package vm prevents clean emacs27 start"):

Hi.  Yes, also, it works for me too.

I think the right thing to do is probably to downgrade this bug until
we are able to come up with a better repro.  You're aware of
emacs -q ?

TBH I'm no longer sure, reading this report, that your bug is anytbing
to do with VM.  Maybe the message about cl is a red herring.

In a clean sid setup I don't get the message about cl any more.  I
forget what the details of that were but I think it was in one of
emacs's dependencies.  Maybe it's been sorted out.

$ emacs -q -batch -f save-buffers-kill-emacs
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/50vm.el (source)...
Loading /etc/emacs/site-start.d/50vm-init.el (source)...

$

Regards,
Ian.
#977918#22
Date:
2021-01-18 14:03:10 UTC
From:
To:
On 18 January 2021 at 13:47, Ian Jackson wrote:
| Control: priority -1 normal
|
| Dirk Eddelbuettel writes ("Bug#977918: vm: Package vm prevents clean emacs27 start"):
| > And of course in a minimal container with just emacs27 and vm the issue does
| > not reproduce. While I have a lot of general programming stuff in .emacs,
| > there is not that much relative to vm so I am a little ... stumped.
|
| Hi.  Yes, also, it works for me too.

Great. Good to know. I am itching to get to emacs27 and just tried wanderlust
and was underwhelmed. Preference to stick with vm :)

| I think the right thing to do is probably to downgrade this bug until

Agreed.

| we are able to come up with a better repro.  You're aware of
| emacs -q ?

Yes, but even after more than a quarter centure of using Emacs I am still a
doofus when it comes to Elisp and debugging.

| TBH I'm no longer sure, reading this report, that your bug is anytbing
| to do with VM.  Maybe the message about cl is a red herring.

Now that you say that I recall that the actual issue was a badly rendering
buffer (using VM) which I then later also encountered in one programming
language I only use rarely, and it turned out to be triggered by a
current-line-highlighting function / package / trick which I turned. So maybe
I should just try again.

| In a clean sid setup I don't get the message about cl any more.  I
| forget what the details of that were but I think it was in one of
| emacs's dependencies.  Maybe it's been sorted out.
|
| $ emacs -q -batch -f save-buffers-kill-emacs
| Loading /etc/emacs/site-start.d/00debian.el (source)...
| Loading /etc/emacs/site-start.d/50autoconf.el (source)...
| Loading /etc/emacs/site-start.d/50vm.el (source)...
| Loading /etc/emacs/site-start.d/50vm-init.el (source)...
|
| $

Yes, I should bite the bullet, back up my ~/.emacs and try again with vm.

Thanks for the follow-up!

Dirk