Re: strange characters in lbdb file make mutt throw "standard input "

* Patrick Shanahan [2016-06-16 00:25]: > * Peter P. [06-15-16 16:32]: > > * Marcelo Laia [2016-06-15 21:00]: > > > Em 15 de jun de 2016 15:41, "Peter P." > > > escreveu: > > > > > > > > I found out

Re: strange characters in lbdb file make mutt throw "standard input "

* Peter P. [06-15-16 16:32]: > * Marcelo Laia [2016-06-15 21:00]: > > Em 15 de jun de 2016 15:41, "Peter P." escreveu: > > > > > > I found out that the way lbdb collects the addresses from mails I send > > > from mutt

Re: strange characters in lbdb file make mutt throw "standard input "

* Marcelo Laia [2016-06-15 21:00]: > Em 15 de jun de 2016 15:41, "Peter P." escreveu: > > > > I found out that the way lbdb collects the addresses from mails I send > > from mutt via lbdb-fetchaddr will create an iso-8859-15 file unless > >

[SPAM?] Re: [SPAM?] strange characters in lbdb file make mutt throw "standard input "

he database from bash works somehow (using the > lbdbq command) and only replacing the umlaut with a question mark > symbol, the query function from within mutt throws > "standard input ". I found out that the way lbdb collects the addresses from mails I send from mutt via lbdb-f

[SPAM?] strange characters in lbdb file make mutt throw "standard input "

, the query function from within mutt throws "standard input ". This error message sounds a lot like grep, and I suspect mutt (or lbdb) to just grep the database file when searching. Now grep has flag (-a) that forces it to treat the input file(s) as ascii whatsoever and I am wondering if

Re: standard input

> If I remove the ^ from Inês in m_inmail.list, I got the correct way: > […] > So, I will need to remove all sign from my m_inmail.list? Are there > some way to by pass this? The software you're using to edit m_inmail.list (a text editor?) probably adds a BOM at the beginning of the file; try

Re: standard input

On 23/05/16 at 10:53pm, Patrice Levesque wrote: > You may try > directly grepping in your file to see if you get the same message, by > searching for something you know is in your addressbook, like: > > grep email_address /home/user/.lbdb/m_inmail.list > > If so, you may want to check that

Re: standard input

> standard input Just a hunch, but this looks like what `grep` spits out when fed a binary stream; many lbdb commands use `grep` internally. You may try directly grepping in your file to see if you get the same message, by searching for something you know is in your addressbook, l

Re: send-hook ignored depending on standard input?

On Thu, May 02, 2002 at 09:29:33AM -0700, Michael Elkins [EMAIL PROTECTED] wrote a message of 14 lines which said: It's not an error in your muttrc, send-hooks have never been executed in batch mode. Off hand I can't remember why this is (perhaps there is no good reason). It seems

send-hook ignored depending on standard input?

I have a send-hook which seems to work fine: send-hook '@ripe.net' 'my_hdr X-NCC-Regid: fr.gitoyen' for interactive use. But when I use mutt with the standard input redirected from a program: dosomething | mutt -s MODIFY [EMAIL PROTECTED] the custom header is not appended at all. If I

Re: send-hook ignored depending on standard input?

' 'my_hdr X-NCC-Regid: fr.gitoyen' for interactive use. But when I use mutt with the standard input redirected from a program: dosomething | mutt -s MODIFY [EMAIL PROTECTED] the custom header is not appended at all. If I replace the send-hook by a direct call to my_hdr, it works. So

Loading standard input as mailbox

I can't pipe a startup mailbox to mutt, because cat mailbox | mutt is treated as an instruction to mail what is piped in. Some Unix commands use the filename "-" as an alias for standard input, but cat mailbox | mutt -f - does not work. Of course, this trivial example can

Re: Loading standard input as mailbox

On Wed, Mar 14, 2001 at 12:25:34PM +0200, Dirk Laurie wrote: I can write a little script, e.g. # /bin/sh MBOX=$$ cat /tmp/$MBOX mutt -f /tmp/$MBOX rm /tmp/$MBOX but mutt seems to know that it is not being invoked from a terminal and tries to go into send mode. Am I missing a