hi,
It seems that mutt can not give to users the cursor's position while
reading mail , this is a bit uncomfortable for me ,
Is there mothod which can make mutt display cursor out ? or custom certain
key-bindings .
thanks!
* Gary Johnson [2012-11-21 06:54]:
> On 2012-11-21, horse_rivers wrote:
>> in my mutt mailbox , I do not know why all mails contain so many
>> useless message text , as below:
>>
>> Received: by x
>> Received: from
>> envelope-from xxx
>>
>> R
/ horse_rivers wrote on Wed 21.Nov'12 at 17:33:22 +0800 /
> hi,
>
> It seems that mutt can not give to users the cursor's position while
> reading mail , this is a bit uncomfortable for me ,
> Is there mothod which can make mutt display cursor out ? or custom certain
> key-bindings .
/ To mutt-users@mutt.org wrote on Sat 10.Nov'12 at 7:39:33 + /
> / David Champion wrote on Fri 9.Nov'12 at 15:00:44 -0600 /
> > Python option:
> > $ easy_install parsedatetime
> > $ python
> > >>> from parsedatetime.parsedatetime import Calendar
> > >>> import time
> > >>> rfc822format = '%
On Tue, Nov 20, 2012 at 11:59:55AM -0600, David Young wrote:
> >On Tue, Nov 20, 2012 at 04:42:13PM +, John Long wrote:
[…]
> > Mail and news need to have sane line lengths. 72 or 76 chars are common. It
> > makes people look like AOL groupies when they post 500 character lines. Many
> > of us
On Tue, Nov 20, 2012 at 03:34:13PM -0500, Peter Davis wrote:
>
> On 11/20/12 3:18 PM, Rado Q wrote:
> >Software can't do magic, or make up for human failures. Sometimes
> >the responsibility is with the user, not the code.
>
> Nope. Totally wrong. The responsibility is entire with the design
=- Jamie Paul Griffin wrote on Wed 21.Nov'12 at 9:49:25 + -=
> BTW, I hope you like my new 72 column line-wrapped mail.
Yes, very much... I even only read your response rather than OP. :)
> It looks beautiful doesn't it and I hope it shows my total
> commitment to respect those reading it.
On Tue, Nov 20, 2012 at 10:19:25PM +, Jamie Paul Griffin wrote:
[…]
> My confusion is simply due to the fact that when my emails come
> through from mutt's mailing list manager to my server and I read them
> with mutt, I don't experience the readability issues others seem to.
> It's not somethi
Sorry for late reply, postponed then forgot to send...
=- Tony's unattended mail wrote on Tue 20.Nov'12 at 21:02:56 + -=
> E.g. if you use a linefeed to end the line of a peom, and then you
> also use an identical linefeed to guess at where to break a stream
> of text in a paragraph, it's unr
On Tue, Nov 20, 2012 at 08:39:02PM +, Tony's unattended mail wrote:
> compose with no linefeeds, except when a linebreak is really needed (a
> peom, for example). The the rendering software can wrap where it
> makes the most sense to, and honor the existing linefeeds that are
> important. The
On Tue, Nov 20, 2012 at 10:01:41AM +, Jamie Paul Griffin wrote:
>
> I don't like vim. I prefer the old vi, so i'd have to set it in ~/.exrc which
> mean all files will be line wrapped which is why I haven't done so already.
> I'll see if theres a muttrc macro or setting I can use to set line
=- Chris Green wrote on Wed 21.Nov'12 at 11:51:52 + -=
> On Tue, Nov 20, 2012 at 10:01:41AM +, Jamie Paul Griffin wrote:
> >
> > I don't like vim. I prefer the old vi, so i'd have to set it in
> > ~/.exrc which mean all files will be line wrapped which is why I
> > haven't done so already
/ Rado Q wrote on Wed 21.Nov'12 at 13:00:12 +0100 /
> =- Chris Green wrote on Wed 21.Nov'12 at 11:51:52 + -=
>
> > On Tue, Nov 20, 2012 at 10:01:41AM +, Jamie Paul Griffin wrote:
> > >
> > > I don't like vim. I prefer the old vi, so i'd have to set it in
> > > ~/.exrc which mean all file
=- Jamie Paul Griffin wrote on Wed 21.Nov'12 at 12:14:25 + -=
> > > > I don't like vim. I prefer the old vi, so i'd have to set it in
> > > > ~/.exrc which mean all files will be line wrapped which is why I
> > > > haven't done so already. I'll see if theres a muttrc macro or
> > > > setting I
On Tue, Nov 20, 2012 at 07:54:28PM +, Tony's unattended mail wrote:
> Proper etiquette is established by those in a region, or in a
> group.. it's based on where you are. If you enter a village where
> everyone does something, that *is* the etiquette, by definition. To
> go against it is to l
On Tue, Nov 20, 2012 at 12:52:58PM -0600, David Champion wrote:
> * On 19 Nov 2012, Chris Bannister wrote:
> > Ouch! Could you please set the "line wrap" value in your editor to a
> > sane value? 72 characters seems to be the recommended setting.
> >
> > (I though you had mistakenly sent this mai
/ Rado Q wrote on Wed 21.Nov'12 at 13:31:58 +0100 /
> =- Jamie Paul Griffin wrote on Wed 21.Nov'12 at 12:14:25 + -=
>
> > > > > I don't like vim. I prefer the old vi, so i'd have to set it in
> > > > > ~/.exrc which mean all files will be line wrapped which is why I
> > > > > haven't done so
* horse_rivers [11-21-12 04:34]:
...
> It seems that mutt can not give to users the cursor's position
> while reading mail , this is a bit uncomfortable for me , Is there
> mothod which can make mutt display cursor out ? or custom certain
> key-bindings .
a little different but it is
* Chris Bannister [11-21-12 06:32]:
> On Tue, Nov 20, 2012 at 08:39:02PM +, Tony's unattended mail wrote:
> > compose with no linefeeds, except when a linebreak is really needed (a
> > peom, for example). The the rendering software can wrap where it
> > makes the most sense to, and honor the
=- Jamie Paul Griffin wrote on Wed 21.Nov'12 at 13:27:04 + -=
> I've just not come across this issue with my editor/mail on other
> lists where many users don't use or seem to care much about line
> wrapping, although the other stuff is picked up on quickly.
Resignation & submissiveness to th
/ Rado Q wrote on Wed 21.Nov'12 at 15:06:08 +0100 /
> =- Jamie Paul Griffin wrote on Wed 21.Nov'12 at 13:27:04 + -=
>
> > I've just not come across this issue with my editor/mail on other
> > lists where many users don't use or seem to care much about line
> > wrapping, although the other stu
Well, when it doesn't work to lecture people who are trying to
communicate, try ignoring them. On public MLs, whenever my "this guy
doesn't know how to communicate effectively" recognizer goes off, I
typically hit 'd' and move on.
If the sender never notices, you probably haven't missed anything.
On Tue, Nov 20, 2012 at 02:54:42PM -0600, David Young wrote:
> On Tue, Nov 20, 2012 at 09:27:19PM +0100, Holger Weiß wrote:
> > * David Young [2012-11-20 11:59]:
> > > On Tue, Nov 20, 2012 at 04:42:13PM +, John Long wrote:
> > > > Take some responsibility for yourself and your content. Post li
/ Mark H. Wood wrote on Wed 21.Nov'12 at 9:56:23 -0500 /
> Well, when it doesn't work to lecture people who are trying to
> communicate, try ignoring them. On public MLs, whenever my "this guy
> doesn't know how to communicate effectively" recognizer goes off, I
> typically hit 'd' and move on.
On Tue, Nov 20, 2012 at 11:27:45PM +, Ken Moffat wrote:
> On Tue, Nov 20, 2012 at 11:59:55AM -0600, David Young wrote:
> > Every now and then some jerk sends me an email reply where their
> > contribution is red. Maybe that is worth fighting about on grounds
> > that that's a poor choice of co
On Tue, Nov 20, 2012 at 10:02:28PM +, Ken Moffat wrote:
> If someone, particularly on a support list, sends an atrociously
> long line, then it becomes *much* harder to select the appropriate
> part of that line/paragraph/epistle and delete the rest of it when
> replying.
Ah, well, when *repl
On Wed, Nov 21, 2012 at 03:23:30PM +, Jamie Paul Griffin wrote:
> / Mark H. Wood wrote on Wed 21.Nov'12 at 9:56:23 -0500 /
>
> > Well, when it doesn't work to lecture people who are trying to
> > communicate, try ignoring them. On public MLs, whenever my "this guy
> > doesn't know how to com
On 2012-11-21, Rado Q wrote:
>
> I guess you put too much interpretation/ meaning in plain-text/
> "text/plain": LF is just that, nothing else, 2 LF are a paragraph,
> that's it.
"Too much" interpretation is an odd stance to take. It's a necessary
amount of interpretation in order to understand
* On 21 Nov 2012, Chris Bannister wrote:
> On Tue, Nov 20, 2012 at 12:52:58PM -0600, David Champion wrote:
> > * On 19 Nov 2012, Chris Bannister wrote:
> > > Ouch! Could you please set the "line wrap" value in your editor to a
> > > sane value? 72 characters seems to be the recommended setting.
>
On Thu, Nov 22, 2012 at 12:09:17AM +1300, Chris Bannister wrote:
>
> Because there are no CR/LF in a paragraph then it is treated all as one
> line.
Interesting, considering that Unix doesn't use CR/LF ... it uses a single
newline instead. So I suppose that means that the entire e-mail, from
th
* On 21 Nov 2012, Chris Bannister wrote:
> Because there are no CR/LF in a paragraph then it is treated all as one
> line. If the first "line" of a paragraph appears at the bottom of the
> screen as yours did then mutt displays "All" on the far right of the
> status line. This gives the impression
On Wed, Nov 21, 2012 at 07:58:15AM +, Jamie Paul Griffin wrote:
> / Matthias Apitz wrote on Wed 21.Nov'12 at 6:54:38 +0100 /
> > Most likely the charset of your terminal does not match the NLS
> > environment (LANG) which you have after login into the Ubuntu. I do not
> > know hyperterminal, i
On Wed, Nov 21, 2012 at 05:02:50PM +, Tony's unattended mail wrote:
> LF means "begin next line now". So as an author posting text to a
> forum, at what point do you need an LF? Not after XX width, because
> that makes poor assumptions about the readers medium (is it an LCD, or
> a phone?).
On Wed, Nov 21, 2012 at 03:23:30PM +, Jamie Paul Griffin wrote:
> People sometimes just reply quickly and therefore forget to adhere
> to some of the netiquette guidelines, it doesn't mean they should be
> ignored.
Yes, it does. If your correspondence is impolite or thoughtless,
then giving
On Wed, Nov 21, 2012 at 07:03:07AM +, Jamie Paul Griffin wrote:
> I, like David do prefer vi over vim not that it's especially relevent,
> so this is great. Being set-up immediately here :-) thanks guys
I'm going to post this one (two-part) comment on preferred editors..
The "right/bes
Mark H. Wood wrote:
> On Tue, Nov 20, 2012 at 10:02:28PM +, Ken Moffat wrote:
> > If someone, particularly on a support list, sends an atrociously
> > long line, then it becomes *much* harder to select the appropriate
> > part of that line/paragraph/epistle and delete the rest of it when
> >
2012/11/21 Will Yardley :
> On Wed, Nov 21, 2012 at 01:41:02AM +0100, E. Prom wrote:
>>
>> When replying to an e-mail with an empty subject, the subject of the
>> answer is set to "Re: your mail".
>
> I thought it was configurable, but didn't find anything from a quick
> search in TFM. Also, it loo
* On 21 Nov 2012, E. Prom wrote:
> 2012/11/21 Will Yardley :
> > On Wed, Nov 21, 2012 at 01:41:02AM +0100, E. Prom wrote:
> >>
> >> When replying to an e-mail with an empty subject, the subject of the
> >> answer is set to "Re: your mail".
> >
> > I thought it was configurable, but didn't find any
On 21/11/12 at 07:00pm, David Champion wrote:
>
> You could create a personal translation, I guess.
>
Have any idea how to do?
--
Marcelo
Brasil (Brazil, for English Speakers)
Linux user number 487797
>You can also hide header lines with 'display-toggle-weed' which is by default
>bound to the key 'h' ...
>
>HTH
>Stefan
thanks! here is another question:how can I modify the default key-binding
of move-down by line?
the default key is ,I want to change it to "down" direction key .
Best
>You can put this parameter into your .muttrc or invoke it when you wish by
>using the command line at the bottom of the mutt screen, ": set pager=tea"
>
>You could even bind it to a key-combination/hot-key.
how to rebind my key ? in muttrc ?
thank you
!
41 matches
Mail list logo
