>>>>> "Daniel" == Daniel Barrett <[email protected]> writes:
> On June 19, 2025, Daniel Barrett wrote:
>> I do see references to vm-biff in a eln-cache file dated yesterday,
>> when I installed emacs 30.1 from snap:
>>
>> $ find ~/.emacs.d -exec grep 'vm-biff' '{}' ;
>> /home/dbarrett/.emacs.d/eln-cache/30.1-b6b3fba3/vm-biff-d121b52d-ad7f8869.eln:
>> binary file matches
>>
>> Removing that cache file seems to have cleared up the problem.
> I celebrated too early. The cache file has returned and so has the biff
> behavior. I'm stumped.
I was going to comment earlier that it looks like all the vm-biff
stuff is xemacs related, and was going to ask if you use it. But from
the sounds of it, you're using emacs 30.1 in X (or Wayland) GUI mode.
Which I never use, I'm always using emacs inside an xterm or screen
session over SSH.
So you're probably on Ubuntu if you're using snap, which sorta implies
it might be more of a packaging problem. What happens if you go back
to the default emacs version is the base OS instead?
I too ran into a bunch of problems with various vm-mime-content-*
settings, because I want to be able to view the URLs easily so I can
cut'n'paste them into a browser when I want to. And converting HTML
into plain UTF8 (or ascii) was painful.
I think I'd still recommend trying to trim back your .vm (and .emacs*)
settings to the system defaults. I know I've got 30+ years of cruft
in my .emacs too! *grin* But that helps limit the problem space to
find the solution.
A big shout out to Mark for helping bring back some development on the
code too!
John
