Joel J. Adamson | 5 May 17:55 2010
Face
Picon

Bash completion

<#secure method=pgpmime mode=sign>
Hello,

When I source /usr/share/doc/nmh-1.3/COMPLETION-BASH I get the following
error:

somehost: ~ > source /usr/share/doc/nmh-1.3/COMPLETION-BASH 
bash: /usr/share/doc/nmh-1.3/COMPLETION-BASH:23: syntax error near unexpected token `('
bash: /usr/share/doc/nmh-1.3/COMPLETION-BASH:23: `        \++([a-zA-Z_]) )'

There seem to be a lot of unbalanced parentheses in this file; I have
fixed those I could find (see attached patch).  However after I source
it again I get this error:

bash: have: command not found

The first line of the file is "have show &&"

Is this a portability issue (is "have" a builtin command for some
installations of bash?  I can't find it in any documentation), or am I
not supposed to source it?  How else would I load it?

The zsh completion worked really well, so using mh from the command-line
was a breeze.  However, since switching to bash I have not had
completion and it's now a chore (for when I'm not using Emacs).  

Thanks for any help you can offer,

Joel

(Continue reading)

Yoshi Rokuko | 8 May 20:18 2010
Picon

Unseen-Sequence not set with rcvstore

my Unseen-Sequence is not set up or something?
I use rcvstore with procmail and my mh_profile
looks like that:

Path: Mail
repl: -annotate
replx: -filter replxfilt -form replxcomps
send: -attach X-MH-Attachment
whatnow: -attach X-MH-Attachment
Unseen-Sequence: new
mhshow-show-image: %p/usr/bin/feh '%f'
mhshow-show-text/html: 

I thought having something like `Unseen-Sequence: new'
in my profile is enough ?

Any help is much appreciated

Best regards, Yoshi 

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers

Yoshi Rokuko | 8 May 21:28 2010
Picon

Re: Unseen-Sequence not set with rcvstore

I found the problem: for whatever reason I am not allowed
to choose `new' as a sequence name.

Sorry for the noise.

Best regards, Yoshi

;::::::::::::::::::::::: Yoshi Rokuko :
> my Unseen-Sequence is not set up or something?
> I use rcvstore with procmail and my mh_profile
> looks like that:
> 
> Path: Mail
> repl: -annotate
> replx: -filter replxfilt -form replxcomps
> send: -attach X-MH-Attachment
> whatnow: -attach X-MH-Attachment
> Unseen-Sequence: new
> mhshow-show-image: %p/usr/bin/feh '%f'
> mhshow-show-text/html: 
> 
> I thought having something like `Unseen-Sequence: new'
> in my profile is enough ?
> 
> Any help is much appreciated
> 
> Best regards, Yoshi 

_______________________________________________
Nmh-workers mailing list
(Continue reading)

Jerrad Pierce | 8 May 21:33 2010

Re: Unseen-Sequence not set with rcvstore

>I found the problem: for whatever reason I am not allowed
>to choose `new' as a sequence name.

From mh-sequence(5):

       There  is  also  a  special "reserved" message name "new" which is
       used by the mhpath command.
--

-- 
Free map of local environmental resources: http://CambridgeMA.GreenMap.org
--
MOTD on Pungenday, the 55th of Discord, in the YOLD 3176:
Go away or I will replace you with a perl one-liner

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers

David Levine | 9 May 16:55 2010
Picon

Re: Bash completion

Joel wrote:

> Hello,
> 
> When I source /usr/share/doc/nmh-1.3/COMPLETION-BASH I get the following
> error:
> 
> somehost: ~ > source /usr/share/doc/nmh-1.3/COMPLETION-BASH
> bash: /usr/share/doc/nmh-1.3/COMPLETION-BASH:23: syntax error near
> unexpected token `('
> bash: /usr/share/doc/nmh-1.3/COMPLETION-BASH:23: `        \++([a-zA-Z_]))'
> 
> There seem to be a lot of unbalanced parentheses in this file; I have
> fixed those I could find (see attached patch).

I'm just guessing, but are those parenthesis pairs needed?
Maybe remove them?  I don't know if quoting the patterns, as you
did in your fix, works properly.

Adding the leading open paren, which you only did on line 23,
doesn't seem right.  The close paren has significance in a case
statement and should not be matched with an open paren.

> However after I source it again I get this error:
> 
> bash: have: command not found
> 
> The first line of the file is "have show &&"
> 
> Is this a portability issue (is "have" a builtin command for some
(Continue reading)


Gmane