Re: mailing list subject line tags
/ Jeremy Kitchen wrote on Tue 30.Oct'12 at 15:32:47 -0700 / > On Tue, Oct 30, 2012 at 05:08:55PM -0500, Derek Martin wrote: > > Bizzare. The only factor which is obvious to me as a possible > > differentiating factor is that the first is quoted printable, and the > > second is plain text. I'm assuming that the first was QP because > > there was a line that started with "from", whereas the second had > > none. I can't for the life of me figure out why that would be happening > > though... I thought it might be because I was not setting my charset > > (in gnupg options), and using UTF-8 (the default of iso-8859-1 is > > assumed, according to the docs). > > for the record, I'm also seeing a failed signature on this post. > > -Jeremy yes, i'm seeing this behaviour as well.
Re: ACS characters in Terminal.app
/ Dennis Preiser wrote on Tue 30.Oct'12 at 14:15:45 +0100 /
> On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
> > This may just be an issue with the Terminal program in OS X, but I'm
> > having some problems with the ACS characters in the threading (I'm not
> > setting $ascii_chars) having breaks between them.
> >
> > The behavior can be seen here:
> > http://soulrebels.com/mutt_threads.png
>
> This might be an issue with the font in Terminal.app. I use menlo 12 pt
> and the threading looks fine. Try a different font to see if the problem
> goes away. And make sure that no additional line spacing is set
> ("Terminal.app -> Preferences -> Settings -> Text -> Change -> Line
> Spacing").
>
> Dennis
altering the line spacing shouldn't make any difference. I have changed that
for some of the different terminal.app profiles I have set up on my lion
machine and it doesn't affect the thread tree at all. In fact the only time
i've had a problem with the thread tree not displaying properly is when i've
been setting up my locales on my OpenBSD machine using urxvt and uxterm.
Re: ACS characters in Terminal.app
On 31Oct2012 08:52, Jamie Paul Griffin wrote:
| / Dennis Preiser wrote on Tue 30.Oct'12 at 14:15:45 +0100 /
| > On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
| > > This may just be an issue with the Terminal program in OS X, but I'm
| > > having some problems with the ACS characters in the threading (I'm not
| > > setting $ascii_chars) having breaks between them.
| > >
| > > The behavior can be seen here:
| > > http://soulrebels.com/mutt_threads.png
| >
| > This might be an issue with the font in Terminal.app. I use menlo 12 pt
| > and the threading looks fine. Try a different font to see if the problem
| > goes away. And make sure that no additional line spacing is set
| > ("Terminal.app -> Preferences -> Settings -> Text -> Change -> Line
| > Spacing").
|
| altering the line spacing shouldn't make any difference.
It affects the horizontal gaps between the lines of text. I expect with
a line spacing of 0 the verticals all join up. (Hacks briefly with
iTerm2... Yep, they all join up, but the ffect is ghastly for iTerm and
my preferred font:-)
The OP's problem isn't the connectors not being drawn (possible with
fonts and locales) but with then being drawn but with gaps due to the
line spacing.
--
Cameron Simpson
The following 3 lines are classified as a munition. Stupid, isn't it?
#!/bin/perl -sp0777i
Apple Mail mishappen messages hide attachments, and a workaround
Apple Mail has concealed attachments from me for the last time I hope! I noted a while ago that Apple Mail puts attachments inside the HTML half of the multipart/alternative container instead of outside in an outer multipart/mixed. If you've set up to prefer the plain text half mutt doesn't show you the attachment. I've put a message-hook workaround on the COnfigTricks wiki page: http://wiki.mutt.org/?ConfigTricks but it feels a little special purpose. Suggestions? Cheers, -- Cameron Simpson My motto is, 'Do it my way or watch your butt.' - Nathan Arizona
Re: ACS characters in Terminal.app
On Wed, Oct 31, 2012 at 08:52:08AM +, Jamie Paul Griffin wrote:
> / Dennis Preiser wrote on Tue 30.Oct'12 at 14:15:45 +0100 /
>
>> On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
>> > The behavior can be seen here:
>> > http://soulrebels.com/mutt_threads.png
>>
>> This might be an issue with the font in Terminal.app. I use menlo 12 pt
>> and the threading looks fine. Try a different font to see if the problem
>> goes away. And make sure that no additional line spacing is set
>> ("Terminal.app -> Preferences -> Settings -> Text -> Change -> Line
>> Spacing").
>
> altering the line spacing shouldn't make any difference. I have changed that
> for some of the different terminal.app profiles I have set up on my lion
> machine and it doesn't affect the thread tree at all.
The Increase of the line spacing leads to gaps between the vertical
lines. At least at my Mac (10.8.2, Terminal.app Version 2.3 (309)):
Line spacing 1.0:
Line spacing 1.3:
Dennis
Re: ACS characters in Terminal.app
/ Cameron Simpson wrote on Wed 31.Oct'12 at 20:25:32 +1100 /
> On 31Oct2012 08:52, Jamie Paul Griffin wrote:
> | / Dennis Preiser wrote on Tue 30.Oct'12 at 14:15:45 +0100 /
> | > On Mon, Oct 29, 2012 at 10:02:28PM -0700, Will Yardley wrote:
> | > > This may just be an issue with the Terminal program in OS X, but I'm
> | > > having some problems with the ACS characters in the threading (I'm not
> | > > setting $ascii_chars) having breaks between them.
> | > >
> | > > The behavior can be seen here:
> | > > http://soulrebels.com/mutt_threads.png
> | >
> | > This might be an issue with the font in Terminal.app. I use menlo 12 pt
> | > and the threading looks fine. Try a different font to see if the problem
> | > goes away. And make sure that no additional line spacing is set
> | > ("Terminal.app -> Preferences -> Settings -> Text -> Change -> Line
> | > Spacing").
> |
> | altering the line spacing shouldn't make any difference.
>
> It affects the horizontal gaps between the lines of text. I expect with
> a line spacing of 0 the verticals all join up. (Hacks briefly with
> iTerm2... Yep, they all join up, but the ffect is ghastly for iTerm and
> my preferred font:-)
>
> The OP's problem isn't the connectors not being drawn (possible with
> fonts and locales) but with then being drawn but with gaps due to the
> line spacing.
I understand that, it has always been that way (since i've used Macs anyway).
It doesn't bother me especially so long as the text content is properly
displayed. I tried iTerm2 but I didn't like it much. For me the default
Terminal in Mac OS X renders a nicer display IMO. But then i spend little time
on my Mac, mostly I just use my BSD machines and urxvt.
Re: R�cksendung (Nr. E-A-2172) abgeschlossen
On Tue, Oct 30, 2012 at 10:06:45PM +0100, Matthias Apitz wrote: > I have mail in mutt with the an encoded Subject: line which seems to decode > wrong (the German Umlaut ü is not shown); how could I decode the line > > Subject: > =?UTF-8?B?Uu+/vWNrc2VuZHVuZyAoTnIuIEUtQS0yMTcyKSBhYmdlc2NobG9zc2Vu?= > > to UTF-8 chars to check what is wrong? Thanks You can use the "base64" command on the part between "=?UTF-8?B?" and "?=": $ echo -n 'Uu+/vWNrc2VuZHVuZyAoTnIuIEUtQS0yMTcyKSBhYmdlc2NobG9zc2Vu' | base64 -d Looking at the result, where you are supposed to have a "ü", you get the hexadecimal number 0xEFBFBD. This is the UTF-8 value of character U+FFFD, which is describe as "REPLACEMENT CHARACTER" in Unicode standard. My guess is that "ü" was originally correctly written, then read with a mail program or operating system not able to understand or display it. Because of this the "replacement character" was used, and then reused in a mail reply. First time I see that. -- Bernard Massot
Re: ACS characters in Terminal.app
On Wed, Oct 31, 2012 at 08:25:32PM +1100, Cameron Simpson wrote: > On 31Oct2012 08:52, Jamie Paul Griffin wrote: > The OP's problem isn't the connectors not being drawn (possible with > fonts and locales) but with then being drawn but with gaps due to the > line spacing. Actually, the way I interpreted it from the screenshot is that the bars weren't lining up vertically, and that I believe is just a font issue. I have the same horizontal gaps, but I don't see that as being a huge problem, really. I think mutt looks just fine as is :) -Jeremy pgpYC2gbgzy5F.pgp Description: PGP signature
Re: ACS characters in Terminal.app
On Wed, Oct 31, 2012 at 11:44:50AM +0100, Dennis Preiser wrote:
> On Wed, Oct 31, 2012 at 08:52:08AM +, Jamie Paul Griffin wrote:
> > / Dennis Preiser wrote on Tue 30.Oct'12 at 14:15:45 +0100 /
> >> This might be an issue with the font in Terminal.app. I use menlo
> >> 12 pt and the threading looks fine. Try a different font to see if
> >> the problem goes away. And make sure that no additional line
> >> spacing is set ("Terminal.app -> Preferences -> Settings -> Text ->
> >> Change -> Line Spacing").
> > altering the line spacing shouldn't make any difference. I have
> > changed that for some of the different terminal.app profiles I have
> > set up on my lion machine and it doesn't affect the thread tree at
> > all.
> The Increase of the line spacing leads to gaps between the vertical
> lines. At least at my Mac (10.8.2, Terminal.app Version 2.3 (309)):
Yeah, I can reproduce the gaps even when using Menlo.
But using Monaco (which, if memory serves, may even be the default font)
results in the gaps, even with line spacing and character spacing set to
1. Also, if you look at the screenshot carefully, you can see that the
lines don't seem to align perfectly horizontally either. Anyway, I
submitted a bug report with Apple (bug # 12604329), so thanks for the
suggestions.
Of the other fixed fonts, Courier also seems to exhibit the problem.
Courier new and Anandale Mono do not.
/wby
Re: ACS characters in Terminal.app
On Wed, Oct 31, 2012 at 11:42:59AM -0700, Will Yardley wrote: > Also, if you look at the screenshot carefully, you can see that the > lines don't seem to align perfectly horizontally either. Actually, this part may have been due to character spacing having been off by a tiny bit. I had already corrected it, and it aligns properly side-to-side now. w
iTerm vs Terminal (was: ACS characters in Terminal.app)
On 31Oct2012 11:12, Jamie Paul Griffin wrote: | I understand that, it has always been that way (since i've used Macs | anyway). It doesn't bother me especially so long as the text content | is properly displayed. Me too. In fact I hadn't even noticed until the post. | I tried iTerm2 but I didn't like it much. For me | the default Terminal in Mac OS X renders a nicer display IMO. But then i | spend little time on my Mac, mostly I just use my BSD machines and urxvt. I like iTerm2 for the following reasons: - focus follows mouse - selecting text can be set to set the cut buffer immediately, no %C needed. Like X11. - horizontal and vertical pane tiling I've bound shift-%V to open a new vertical pane (splits the current pane vertically) and shift-%T to open a new horizontal pane (splits the current pane horizontally). This is outstandingly useful for working in multiple shells. I do a lot of remote admin and opening shells on a bunch of machines nicely arranged for coordinated work is very pleasing. And of course I've spent some time tuning fonts and colours, and made things slightly transparent with a slight brightening for the currently focussed pane. iTerm2 has lots of features, but the ones above are the real winners for me. Cheers, -- Cameron Simpson Sattinger's Second Law: Even though you've plugged it in, it still won't work until you switch it on.
Re: iTerm vs Terminal (was: ACS characters in Terminal.app)
On Thu, Nov 01, 2012 at 09:01:20AM +1100, Cameron Simpson wrote: > | I tried iTerm2 but I didn't like it much. For me > | the default Terminal in Mac OS X renders a nicer display IMO. But then i > | spend little time on my Mac, mostly I just use my BSD machines and urxvt. > > I like iTerm2 for the following reasons: > > - horizontal and vertical pane tiling > I've bound shift-%V to open a new vertical pane (splits the current > pane vertically) and shift-%T to open a new horizontal pane (splits > the current pane horizontally). > This is outstandingly useful for working in multiple shells. > I do a lot of remote admin and opening shells on a bunch of machines > nicely arranged for coordinated work is very pleasing. You may want to look into tmux :) Then again, nearly 100% of my in-terminal work is done from another, permanently-connected machine, and my mac is just a portal to my linux-box-du-jour. > And of course I've spent some time tuning fonts and colours, and made > things slightly transparent with a slight brightening for the currently > focussed pane. iTerm2 has lots of features, but the ones above are the > real winners for me. I am pretty pleased with Terminal.app from Lion forward, but my work machine is sadly still on Snow Leopard (silly corp IT policy, don't ask) so I tried out iTerm2 again and now I use it primarily on both of my macs. -Jeremy pgpPjGTbftMMI.pgp Description: PGP signature
Re: iTerm vs Terminal (was: ACS characters in Terminal.app)
On Thu, Nov 01, 2012 at 09:01:20AM +1100, Cameron Simpson wrote: > - focus follows mouse You can enable sloppy focus in Terminal.app too (though there's a long-standing and very annoying bug with the interaction between that and *other* applications, which don't have it). % defaults read com.apple.Terminal FocusFollowsMouse YES To set it, you can run: defaults write com.apple.Terminal FocusFollowsMouse -string YES You have to change focus to the app itself via the normal method, but once you're in it, you can use the mouse to focus windows without clicking. w
Re: iTerm vs Terminal (was: ACS characters in Terminal.app)
On 31Oct2012 15:17, Jeremy Kitchen wrote: | On Thu, Nov 01, 2012 at 09:01:20AM +1100, Cameron Simpson wrote: | > | I tried iTerm2 but I didn't like it much. For me | > | the default Terminal in Mac OS X renders a nicer display IMO. But then i | > | spend little time on my Mac, mostly I just use my BSD machines and urxvt. | > | > I like iTerm2 for the following reasons: | > | > - horizontal and vertical pane tiling | > I've bound shift-%V to open a new vertical pane (splits the current | > pane vertically) and shift-%T to open a new horizontal pane (splits | > the current pane horizontally). | > This is outstandingly useful for working in multiple shells. | > I do a lot of remote admin and opening shells on a bunch of machines | > nicely arranged for coordinated work is very pleasing. | | You may want to look into tmux :) Oh, I do want to! I'm still a screen user on the whole and haven't yet wrapped my head around tmux' usage. But if you mean logically subdividing a single _terminal_ window with multiple session displays, no thanks. I've never found it works for me with vi or screen or other in-terminal dividers, including urxvt's internal tabbing support; they all devolve to focus follows mouse or arcane keystrokes to switch focus because the terminal doesn't see the mouse cursor, and they also all devolve to emulated terminals and curses support issues, and the control stuff gets in the way of being a "pure" terminal. Let us not get into cut/paste line ending issues:-) I find it far better to use a terminal emulator like iTerm2 to manage this stuff. Now, that said, I _do_ have use for easy ways to fork off a bunch of nicely split up windows/tabs/panes. I intend spending a day with AppleScript and my "@" convenience script to make it support this syntax: @ h1,2,3:h4,5,h6 h1,2,3 ... where each space separated chunk makes a new tab, each colon separated chunk a new vertical pane and each comma separated chunk a new horizontally split pane within that vertical pane. So that the above with open two tabs, the first with two vertical panes. The first vertical pane would have ssh sessions to hosts "h1" and "h2" and "h3". And so on. I've had the comma syntax for years via a handy script, so all that remains is the parsing for the rest (and figuring out what I have to say to iTerm2 via AppleScript to get it to obey). The other terminal related project on the backburner is a screen (or tmux) based session tracker so that when I lose my remote connections I can easily and intuitively reconnect to them. | Then again, nearly 100% of my in-terminal work is done from another, | permanently-connected machine, and my mac is just a portal to my | linux-box-du-jour. My mac is my portal like yours (though I do a lot of coding locally and push changes out - far far snappier, and one can do it on a train or otherwise offline, pushing later). This email is being written on my home server via ssh, and I've got mutt configured to automatically compose replies in a detachable screen session named after a mangling of the subject line, so I can reconnect later if disconnected (or if I just decide to disconnect from screen and finish composition another time). Thus: [/home/cameron]janus*> scr 1 23168.BACKUP 27237.DOVECOT 3 12992.EMERGE 48218.GETMAIL 59000.MAILFILER 6 31196.WD 74915.WD_BEY2 84793.WD_BEYONWIZ 9 14831.mutt-01nov2012-10:10 10 16970.mutt-27oct2012-14:45 So I could detach right now and reconnect by saying "scr 10" to finish the job. Anyone wanting to see the code for any of the above is quite welcome, BTW. Cheers, -- Cameron Simpson Are you experiencing more Windows95 crashes than the norm? How on earth would you _know_? - John Brook reporting about a new virus
Re: iTerm vs Terminal (was: ACS characters in Terminal.app)
* Cameron Simpson [10-31-12 19:31]: > On 31Oct2012 15:17, Jeremy Kitchen wrote: > | > | You may want to look into tmux :) > > Oh, I do want to! > > I'm still a screen user on the whole and haven't yet wrapped my head > around tmux' usage. > > But if you mean logically subdividing a single _terminal_ window with > multiple session displays, no thanks. I've never found it works for > me with vi or screen or other in-terminal dividers, including urxvt's > internal tabbing support; they all devolve to focus follows mouse or > arcane keystrokes to switch focus because the terminal doesn't see the > mouse cursor, and they also all devolve to emulated terminals and curses > support issues, and the control stuff gets in the way of being a "pure" > terminal. Let us not get into cut/paste line ending issues:-) I have gone over to tmux for > a year now. I have 9 pages, some split. I access my mail and webserver box remotely in a tmux session with pages open to 3 other boxes. I upgraded boxes some years ago and left my web server and mail on the original box. I read my mail via ssh'ing to a tmux session running on the original box. This way I can access the tmux session remotely from anywhere on anyone's box, including windoz running vnc from a usb stick. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: iTerm vs Terminal (was: ACS characters in Terminal.app)
On Thu, Nov 01, 2012 at 10:28:09AM +1100, Cameron Simpson wrote: > On 31Oct2012 15:17, Jeremy Kitchen wrote: > | You may want to look into tmux :) > > Oh, I do want to! [...] > But if you mean logically subdividing a single _terminal_ window with > multiple session displays, no thanks. I've never found it works for > me with vi or screen or other in-terminal dividers, including urxvt's > internal tabbing support; they all devolve to focus follows mouse or > arcane keystrokes to switch focus because the terminal doesn't see the > mouse cursor, and they also all devolve to emulated terminals and curses > support issues, and the control stuff gets in the way of being a "pure" > terminal. Let us not get into cut/paste line ending issues:-) ugh. don't remind me about the cut/paste issues. in your case, screen is fine :) Really, screen is just fine, I just got into tmux because I wanted to see what all the hype was about and now I'm much better with tmux than I ever was with screen. > | Then again, nearly 100% of my in-terminal work is done from another, > | permanently-connected machine, and my mac is just a portal to my > | linux-box-du-jour. > > My mac is my portal like yours (though I do a lot of coding locally and > push changes out - far far snappier, and one can do it on a train or > otherwise offline, pushing later). This email is being written on my > home server via ssh, and I've got mutt configured to automatically > compose replies in a detachable screen session named after a mangling of > the subject line, so I can reconnect later if disconnected (or if I just > decide to disconnect from screen and finish composition another time). > Thus: > > [/home/cameron]janus*> scr > 1 23168.BACKUP > 27237.DOVECOT > 3 12992.EMERGE > 48218.GETMAIL > 59000.MAILFILER > 6 31196.WD > 74915.WD_BEY2 > 84793.WD_BEYONWIZ > 9 14831.mutt-01nov2012-10:10 >10 16970.mutt-27oct2012-14:45 > > So I could detach right now and reconnect by saying "scr 10" to finish > the job. Hrm. I'd be very interested in seeing how this works. I like the idea, but mutt's email editing is modal, right? How does that work with essentially backgrounding an editor? > Anyone wanting to see the code for any of the above is quite welcome, > BTW. Yes, please :) -Jeremy pgpJoc4m5LlbS.pgp Description: PGP signature
