Mark D. Baushke | 1 Nov 05:45 2005
X-Face
Picon

Re: Emacs 20 support


Bill Wohler <wohler <at> newt.com> writes:

> Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:
> 
> > I'm starting to wish emacs-20 would just go away.  Why don't we just
> > quit supporting it?  Debian has...
> 
> I was just thinking the same thing.
> 
> Are there any users out there still using Emacs 20? If so, please speak
> up!

Yes, two of my ISPs that provide shell accounts only provide Emacs 20.4
(FreeBSD) and Emacs 20.7 (GNU/Linux). However, I am not actively using
MH-E on those hosts, so I am somewhat ambivalent about continuing
support.

> Otherwise, we'll probably discontinue Emacs 20 support in version 8.

I agree that version 8 would be the right time to discontinue Emacs 20
support.

	-- Mark
Eric Jensen | 1 Nov 15:52 2005

Re: How can I get Spotlight to index MH files?

Hi again,

Sorry to respond to my own message, but there's a much better way to do
this than what I suggested yesterday, it occurs to me.  What you really
want is for the MH message files to be (correctly) identified as text
files, so that then Spotlight will index them.  So, this works for me:

1.  From the Terminal window, change the type of all MH files to text:

    find /path/to/mh/top-level/directory/ -name "[0-9]*" -type f \ 
	 -exec /Developer/Tools/SetFile -t TEXT {} \;

2.  Now that the system knows they are text files, index them for Spotlight: 

    mdimport /path/to/mh/top-level/directory/ 

You'll need to have Developer Tools installed in order to do this
(though there may be other utils that can do it), and you'll need to run
that 'find' command periodically (perhaps via cron) to keep up with new
messages.  I don't know whether the Spotlight indexing will occur
automatically once they are recognized as text files or not, but it's
easy enough to do right after the type change if you're running that
periodically anyway.

I copied over some of my MH folders to OS X and tested this out, and it
seems to work fine for me. 

Hope this is useful for others,

Eric
(Continue reading)

Massimo Bernaschi | 1 Nov 09:40 2005
Picon

mh-e files with #

--------
Please, excuse me if the following is a dumb question:
I found I have tons of files in my mh-e folders with a # character at the beginning and
at the end of the "regular" name, e.g., #823#.
I am pretty sure these corresponds to messages I deleted. 
May I remove them safely "by hand"? Is there a way to prevent these files from appear?
Thanks in advance and best regards,
Massimo

--- Massimo Bernaschi: Istituto Applicazioni del Calcolo ---- 
|  IAC-CNR                  | e-mail: massimo <at> iac.cnr.it    |
|  V.le del Policlinico 137 | phone: +39 06 88470229        |
|  00161 Roma - ITALY       | fax:   +39 06 4404306         |
------------------------------------------------------------|
|See http://www.iac.cnr.it/~massimo for my GPG public key   |
-------------------------------------------------------------

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Bill Wohler | 1 Nov 18:21 2005
Picon
Picon

Re: mh-e files with #

Massimo Bernaschi <massimo <at> iac.cnr.it> wrote:

> I found I have tons of files in my mh-e folders with a # character at
> the beginning and at the end of the "regular" name, e.g., #823#. I am
> pretty sure these corresponds to messages I deleted. May I remove them
> safely "by hand"?

See "03.08 How can I automatically delete MH backup files?" in
http://www.newt.com/faq/mh.faq

> Is there a way to prevent these files from appear?

The answer is in the rmm man page.

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Bill Wohler | 1 Nov 18:44 2005
Picon
Picon

Re: mh-e files with #

I forgot the references to the MH book:

http://www.ics.uci.edu/~mh/book/mh/clermm.htm
http://www.ics.uci.edu/~mh/book/mh/rem.htm
http://www.ics.uci.edu/~mh/book/mh/e-rmmer.htm
http://www.ics.uci.edu/~mh/book/mh/pccewca.htm

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Henrik Frisk | 2 Nov 11:40 2005

Re: How can I get Spotlight to index MH files?

> Sorry to respond to my own message, but there's a much better way to do
> this than what I suggested yesterday, it occurs to me.  What you really
> want is for the MH message files to be (correctly) identified as text
> files, so that then Spotlight will index them.  So, this works for me:
> 
> 1.  From the Terminal window, change the type of all MH files to text:
> 
>     find /path/to/mh/top-level/directory/ -name "[0-9]*" -type f \ 
> 	 -exec /Developer/Tools/SetFile -t TEXT {} \;
> 
> 2.  Now that the system knows they are text files, index them for Spotlight: 
> 
>     mdimport /path/to/mh/top-level/directory/ 
> 
> You'll need to have Developer Tools installed in order to do this
> (though there may be other utils that can do it), and you'll need to run
> that 'find' command periodically (perhaps via cron) to keep up with new
> messages.  I don't know whether the Spotlight indexing will occur
> automatically once they are recognized as text files or not, but it's
> easy enough to do right after the type change if you're running that
> periodically anyway.
> 
> I copied over some of my MH folders to OS X and tested this out, and it
> seems to work fine for me. 
> 
> Hope this is useful for others,
> 
> Eric

Great tip. This works! Thanks!
(Continue reading)

Douglas Alan | 3 Nov 02:42 2005
Picon

Re: How can I get Spotlight to index MH files?

Eric Jensen <ejensen1 <at> swarthmore.edu> wrote:

> 1.  From the Terminal window, change the type of all MH files to text:
> 
>     find /path/to/mh/top-level/directory/ -name "[0-9]*" -type f \ 
> 	 -exec /Developer/Tools/SetFile -t TEXT {} \;

> 2.  Now that the system knows they are text files, index them for Spotlight: 
> 
>     mdimport /path/to/mh/top-level/directory/ 

Thanks!  That's exactly what I wanted.  The other way you mentioned
seemed as if it might be a bit problematic, as many binary and
executable files are of ContentType "public.data.

As it turns out, Spotlight is unfortunately a bit squirrelly, in that if
a file has multiple hard links to it, only one of the links will be
recognized by Spotlight.  This undermines a bit the usefulness of having
MH able to keep the same email message in multiple folders.

|>oug

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Bill Wohler | 5 Nov 20:06 2005
Picon
Picon

mh-highlight-citation-p -> mh-highlight-citation-style

The Emacs Lisp coding conventions say:

   * If the purpose of a function is to tell you whether a certain
     condition is true or false, give the function a name that ends in
     `p'.  If the name is one word, add just `p'; if the name is
     multiple words, add `-p'.  Examples are `framep' and
     `frame-live-p'.

However, the option mh-highlight-citation-p is neither a function, nor
is it tested whether it is true or false (in which case it would have a
-flag suffix).

I therefore propose that we rename this option from
mh-highlight-citation-style (or mh-citation-highlighter or ...). Its
values will be "Gnus", "font-lock", "None".

I trust that most folks use the default and won't even notice ;-).

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Peter S Galbraith | 5 Nov 20:19 2005
Picon

Re: mh-highlight-citation-p -> mh-highlight-citation-style

Go for it Bill.  Thanks!

Bill Wohler <wohler <at> newt.com> wrote:

> The Emacs Lisp coding conventions say:
> 
>    * If the purpose of a function is to tell you whether a certain
>      condition is true or false, give the function a name that ends in
>      `p'.  If the name is one word, add just `p'; if the name is
>      multiple words, add `-p'.  Examples are `framep' and
>      `frame-live-p'.
> 
> However, the option mh-highlight-citation-p is neither a function, nor
> is it tested whether it is true or false (in which case it would have a
> -flag suffix).
> 
> I therefore propose that we rename this option from
> mh-highlight-citation-style (or mh-citation-highlighter or ...). Its
> values will be "Gnus", "font-lock", "None".
> 
> I trust that most folks use the default and won't even notice ;-).

--

-- 
Peter S. Galbraith, MH-E developer  <p.galbraith <at> globetrotter.net>
GPG key 1024/D2A913A1 - 97CE 866F F579 96EE  6E68 8170 35FF 799E
6623'rd GNU/Linux user at the Counter - http://counter.li.org/

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
(Continue reading)

Bill Wohler | 5 Nov 20:26 2005
Picon
Picon

Manual, 8.0, and incompatible changes

In case folks haven't noticed, I am making a push to finish the manual
update. We are planning on making a major MH-E release--8.0--to coincide
with the completion of the new manual.

I'm also planning to change the version of the number of the manual from
its current 1.3 to 8.0 so that it matches the version of the software. I
find that this is much more clear in packaging systems such as Debian
that provide the documentation in a separate package from the software.

While going over the code with a fine comb, I am taking advantage of the
major upgrade to make little--but incompatible--cleanups such as the
mh-highlight-citation-p renaming (that's why MH-E is in an alpha release
series--7.8*). For the most part, I announce my intentions either here
or on mh-e-devel, and the changes are all definitely documented in the
release notes (MH-E-NEWS). The result will be a more consistent, easier
to use, interface. I'm assuming (and hoping) our users are amenable to
that.

Schedule? My previous forecasts have been overcome by events, but I
would like to have the manual done within the month. Once that is done,
we'll make a beta release (7.90), work on licensing issues with the
manual (Debian wants GPL, GNU Emacs wants FDL), and release MH-E 8.0
with manual. With luck, I'll get it in CVS Emacs in time for the Emacs
22 release. Only time will tell if all of this comes to pass.

Then I can look for a job! ;-)

As usual, comments about this, as well as anything else related to MH-E,
are welcome and appreciated!

(Continue reading)


Gmane