New home for VM development
Uday S Reddy
Ulrich and I have set up a new project home for VM, which will be
maintained by the "VM development team". Currently, Rob, Ulrich and I
are the members of the team, but as I have mentioned, we do need more
people to get involved. The email address for the team is
vm 'at'lists.launchpad.net (replace 'at' by @)
You can access the new project and its codebase at
http://launchpad.net/vm (shorthand: "lp:vm" in Bazaar)
and
http://launchpad.net/vm/8.0.x (shorthand: "lp:vm/8.0.x" in Bazaar)
The second URL gives you Rob's latest revision for the 8.0.x branch,
with fixes for the character encoding problems found in 8.0.12. I
intend to rlease this as 8.0.13.
The main trunk has the current development version. You can pull the
latest updates from here through Bazaar. (Please don't use the
~reddyuday/viewmail/8.1 branch any more.)
Thanks very much to Ulrich for setting up the team site!
Cheers,
Uday
Sven
> Ulrich and I have set up a new project home for VM, which will be
> maintained by the "VM development team".
Hooray! I am sooo glad to see development going on! Although I have never
used bzr before I just managed to get the newest version (vm-612) up and
running. It really seems to fix my encoding problems (emacs23). Thank you
so much for all the effort you put into this!!!
Two minor issues:
(1) The INSTALL file tells me to "Compile everything by running: make".
make tells me there is no target. I tried "make all" and it tells me
there is no rule for target all. I wonder whether the install
instructions are correct? (It seems to work well without compiling
though.)
(2) At vm startup, there are some rather annoying messages in the
minibuffer:
(taken from *Messages*:)
WARNING: Could not load feature bbdb.
WARNING: Related functions may not work correctly!
WARNING: Could not load feature bbdb-vm.
WARNING: Related functions may not work correctly!
(file-error "Cannot open load file" "bbdb")
Could not load bbdb.el. Related functions may not work correctly!
Having to wait till all these messages are gone it takes longer to get
the new mails. I do not want to use bbdb.
Well, these are really minor issues which do not impair my gratification
about the encoding problems being gone!
> Currently, Rob, Ulrich and I
> are the members of the team, but as I have mentioned, we do need more
> people to get involved.
Do you have any idea on how non-lisp-experts like me can contribute?
Long live the VM development team! :-)
Sven
Uday S Reddy
>
> Hooray! I am sooo glad to see development going on! Although I have never
> used bzr before I just managed to get the newest version (vm-612) up and
> running. It really seems to fix my encoding problems (emacs23). Thank you
> so much for all the effort you put into this!!!
I am really glad you are trying it out and it is working! Rob F himself
deserves a lot of the credit for fixing the encoding problems. It is a
pity that he had to go off before releasing the fixes. Ulrich, Julian
and several others have contributed ideas for the fixes. So it was
really a team effort.
> (1) The INSTALL file tells me to "Compile everything by running: make".
> make tells me there is no target. I tried "make all" and it tells me
> there is no rule for target all. I wonder whether the install
> instructions are correct? (It seems to work well without compiling
> though.)
Unfortunately, it is a bit of a complicated process. The Makefile is
built by configure which is in turn built by autoconf. So, if the
preceding steps didn't work right, the Makefile might not be right. I
am attaching here the Makefile that I get so that you can compare yours
with it.
> (2) At vm startup, there are some rather annoying messages in the
> minibuffer:
>
> (taken from *Messages*:)
> WARNING: Could not load feature bbdb.
> WARNING: Related functions may not work correctly!
> WARNING: Could not load feature bbdb-vm.
> WARNING: Related functions may not work correctly!
> (file-error "Cannot open load file" "bbdb")
> Could not load bbdb.el. Related functions may not work correctly!
This could be a side effect of the fact that you didn't compile the
files. When you run configure, you can use
./configure --with-other-dirs=
(with empty argument for with-other-dirs), which tells the build that
you don't want to use bbdb.
> Do you have any idea on how non-lisp-experts like me can contribute?
You are contributing already by trying out the devo version and giving
us your feedback! But I will share some ideas later for non-programming
contributions that people can make.
> Long live the VM development team! :-)
Amen to that!
Cheers,
Uday
Sven
>> (1) The INSTALL file tells me to "Compile everything by running: make".
>> make tells me there is no target. I tried "make all" and it tells me
>> there is no rule for target all. I wonder whether the install
>> instructions are correct? (It seems to work well without compiling
>> though.)
> Unfortunately, it is a bit of a complicated process. The Makefile is
> built by configure which is in turn built by autoconf. So, if the
> preceding steps didn't work right, the Makefile might not be right. I
> am attaching here the Makefile that I get so that you can compare yours
> with it.
Don't know what is different today, but make runs perfectly now. Sorry, I
probably missed some step yesterday.
>> (2) At vm startup, there are some rather annoying messages in the
>> minibuffer:
>> (taken from *Messages*:)
>> WARNING: Could not load feature bbdb. WARNING: Related functions may
>> not work correctly! WARNING: Could not load feature bbdb-vm. WARNING:
>> Related functions may not work correctly! (file-error "Cannot open load
>> file" "bbdb") Could not load bbdb.el. Related functions may not work
>> correctly!
> This could be a side effect of the fact that you didn't compile the
> files. When you run configure, you can use
>
> ./configure --with-other-dirs=
>
> (with empty argument for with-other-dirs), which tells the build that
> you don't want to use bbdb.
The "--with-other-dirs=" part does not seem to be necessary. With or
without it, when the compiling works, my vm startup is without warnings
and thus much faster (and probably also faster due to the compilation).
Great!
Thank you very much for your help!
Looks like the INSTALL file was and is correct and it was some mistake on
my part.
Very happy with fast and working vm now. :-)
Sven