Kyle Wheeler:
|The indent_string is, like many of mutt's other strings, possible to
|set automatically with a program if it ends with a pipe character...What
|you need to do to get what you want is to escape the pipe (unfortunately,
|twice), so that it isn't recognized as indicatin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, February 8 at 01:55 PM, quoth Randall Hopper:
> Long time mutt user. Recent distro upgrade bumped me to Mutt
> 1.5.16, and in this version, I can't get "indent_string" to work at
> all.
>
> In Mutt,
Hi all,
Long time mutt user. Recent distro upgrade bumped me to Mutt 1.5.16, and
in this version, I can't get "indent_string" to work at all.
In Mutt, I confirm:
indent_string=" |"
text_flowed is unset
But no indent string is applied to most messages at all, and
rmat in my pages? Do you think you ever will?
Do you think you could mistake 000101 with 1900-01-01?
Or maybe mistake a date like 991231 with 2099-12-31?
> I can't even pump ls through sort, with or without a -n flag,
> since AFAIK there is no "minus short date form" flag.
&
ne does an ls. And maybe I don't
want to sort by time, either, because the timestamps may not match up;
maybe these aren't log files but notes I took and I later edited an old
file to expound on something. I can't even pump ls through sort, with or
without a -n flag, since AFAIK t
we use them in these messages
or on webpages? does it matter to your scripts? and
what *exactly* are you doing with that info, anyway?
besides, if your "ls" gets confused with
those short date form then let us know.
Sven [not expecting to hear any complaints
within the next 50 years..]
--
Sven Guckes HOLY WARS of Usenet [EMAIL PROTECTED]
HOLY EDITOR: emacs|viTEXT: text/plain|base64|quoted-printable
HOLY PAGER: less|moreSHELL: sh|bash|ksh|tcsh|zsh tabstop=2|4|8
HOLY textwidth=65|72|80 TABU: indent_string="> "sigdashes=ON
* Vineet Kumar <[EMAIL PROTECTED]> [09-Mon-01 14:46 -0700]:
>
>* Erika Pacholleck ([EMAIL PROTECTED]) [010901 04:46]:
>> [23.08.01 18:45 +0100] Ailbhe Leamy <-- :
>> > On (18/08/01 18:57), David R?hr wrote:
[...snip...]
>> done. Set in mutt indent string to ">" and then change the vi
* Erika Pacholleck ([EMAIL PROTECTED]) [010901 04:46]:
> [23.08.01 18:45 +0100] Ailbhe Leamy <-- :
> > On (18/08/01 18:57), David R?hr wrote:
> > > When I answer a mail mutt always put "> " as quote on the last mail
> > > according to the indent_string
[23.08.01 18:45 +0100] Ailbhe Leamy <-- :
> On (18/08/01 18:57), David Röhr wrote:
> > When I answer a mail mutt always put "> " as quote on the last mail
> > according to the indent_string in my .muttrc.
> >
> > I want "> " only when no ot
On (18/08/01 18:57), David Röhr wrote:
> When I answer a mail mutt always put "> " as quote on the last mail
> according to the indent_string in my .muttrc.
>
> I want "> " only when no other has replyed, but if there already is a
> "> " t
When I answer a mail mutt always put "> " as quote on the last mail
according to the indent_string in my .muttrc.
I want "> " only when no other has replyed, but if there already is a
"> " then i want it to become just ">"
How do I fix th
Hello Mutt Users!
On wto 08 sie 2000 17:43:40 GMT Caster wrote:
> Can anybody tell me why this doesn't work:
> set indent_string=`for x in %n; do echo $x | cut -c 1; done;`
Of course I forgot about send-hook so it just couldn't work...
Eh...
--
lamest
Tomasz Olszewski
[EMAIL PROTECTED]
Caster <[EMAIL PROTECTED]> wrote on Tue, 08 Aug 2000:
> Can anybody tell me why this doesn't work:
> set indent_string=`for x in %n; do echo $x | cut -c 1; done;`
> Normally (when I run it manually from the shell) it works fine (of
> course when I replace %n with some wo
Can anybody tell me why this doesn't work:
set indent_string=`for x in %n; do echo $x | cut -c 1; done;`
Normally (when I run it manually from the shell) it works fine (of
course when I replace %n with some words).
--
Tomasz Olszewski
[EMAIL PROTECTED]
14 matches
Mail list logo
