Re: [MlMt] Any way to prevent auto-correcting two spaces after a period to one?
The autocorrect is system-wide in Cocoa text fields. To change it, go to System Preferences - Keyboard - Text and uncheck “Correct spelling automatically.” Strangely though I can’t replicate this behavior and furthermore why would you want two spaces after a period? Sincerely, Ben Klebe On Sun, Jun 7, 2015 at 1:41 PM, Alan Goldsmith alangoldsm...@gmail.com wrote: ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Any way to prevent auto-correcting two spaces after a period to one?
Oh I guess OP is not composing in plain text? My apologies. Sincerely, Ben Klebe On Sun, Jun 7, 2015 at 1:55 PM, Billy Youdelman bi...@mix.com wrote: Using the composer's plain text mode seems to be one way. As can be seen here. Two spaces. ビリー ヨーデルマん +1 310 839 7673 http://MIX.ORG/ ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Any way to prevent auto-correcting two spaces after a period to one?
No, he’s saying that when the practice began doesn’t matter because it’s not part of 21st century typography. Sincerely, Ben Klebe On Sun, Jun 7, 2015 at 11:46 PM, Eric A. Meyer e...@meyerweb.com wrote: I'll offer my own but of insight: Butterick is right that it doesn't matter. I just wish he and those who follow his view would take that advice to heart, and stop demonstrating to all and sundry that it really does matter to them. On 7 Jun 2015, at 23:21, Ben Klebe wrote: I can only offer this shrewd bit of insight from Matthew Butterick’s excellent Practical Typography: http://practicaltypography.com/one-space-between-sentences.html I know that many people were taught to put two spaces between sentences. I was too. But these days, using two spaces is an obsolete habit. Some say the habit originated in the typewriter era. Others believe it began earlier. But guess what? It doesn’t matter. Because either way, it’s not part of today’s typographic practice. Sincerely, Ben Klebe On Sun, Jun 7, 2015 at 11:12 PM, Gary Hull yh82d7...@yandex.com wrote: On 8 Jun 2015, at 9:40, Eric A. Meyer wrote: On 7 Jun 2015, at 20:16, Gary Hull wrote: On 8 Jun 2015, at 2:44, Ben Klebe wrote: The autocorrect is system-wide in Cocoa text fields. To change it, go to System Preferences - Keyboard - Text and uncheck “Correct spelling automatically.” Strangely though I can’t replicate this behavior and furthermore why would you want two spaces after a period? Please don't open that can of worms on the mailing list!: …he said, and then wrenched the can open further. You noticed that, huh? :-) http://www.slate.com/articles/technology/technology/2011/01/space_invaders.html Although I agree: two spaces after a period should have died with manual monospace typewriters. You and Manjoo are wrong: the wider post-sentence spacing was not a quirky, transient artifact of typewriters or monospace fonts, but has literal centuries of precedent and tradition behind it: http://www.heracliteanriver.com/?p=324 I worked in my middle school's print shop for a year setting lead type from a California case and redistributing the pi, so I know the traditions, and have read all the old pre-ITC typography books that are only available on ABE.com these days. I later worked as a graphic designer in a shop that went through the whole range of phototypography from hand-spaced display type to self-contained Compugraphic machines to Agfa-Compugraphic front-ends to Postscript imagesetters. Not to mention IBM Selectric Composers with Adrian Frutiger-designed fonts on 9-to-the-em grids. The point of books written for compositors is to teach compositors what to do. Writers didn't typeset their own books. Spacing decisions are made by the compositor, based on the font in use, the leading, and the particular letter pair. Today the function of the compositor has been taken over by the combination of the type designer and the particular system in which the font is realized (such as Postscript), which has all sorts of intelligence built into it, and additional intelligence built into the publishing software that drives the output (imagesetter or digital display). Again, the writer shouldn't be trying to force design factors like that in his manuscript (although click-to-publish bloggers have to assume some design responsibility). Fonts are no longer made of lead, you can kern without brass spacers, and you can negatively kern without filing off the lead corners of the font. The way that type looks today is the way that skilled typographers want it to work, and the best of them have simply better taste than the past masters. Old books just look blotchy to modern eyes, although they are beautiful as historical objects. At any rate, double spacer should know that publishers these days have regex routines that manuscripts get run through, fixing things like initial and trailing spaces and high-bit ASCII, and that /\w+/\w/ or the like is built into such routines. So good luck getting double spaces into print at a proper publisher. There was a period, I'll say mostly in the 1960s, 1970s, but also a bit before and after, when many low-budget publications, including many academic and scientific publications, published photographically reduced typed manuscripts. In other words, cheap typesetting was not available yet, and they couldn't afford typesetting. In these cases the style that writers had to follow specified Elite or Courier, double spacing (two returns on the typewriter), the width of margins, the number of lines per page, manual justification (with double spaces to accomplish that, or half spaces, which some typewriters could handle, such as some Olympias), and so on. Universities had typing pools that could produce such manuscripts: They functioned as the typetting departments
[MlMt] FIXMEs in Gmail bindings plist
The Gmail keybindings plist has the following listed as FIXME. Does this mean fix the plist, or add these methods as valid? These options seem much better than toggleReadState: but they don't appear to be on the official keyword list. I = toggleReadState:; // FIXME: Should be ( markAsRead:, nextMessage:); U = toggleReadState:; // FIXME: Should be markAsUnRead: Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Evaluation results
I don't care about a discount and I don't care about 50 EUR. I care about a working work environment and I take the freedom to complain about software that has obvious bugs. I am software developer myself and I am annoyed to see so many little obvious and open issues in your software in a 1.9 release. I have not seen this in any other Mac software so far. Either some features are not very well thought or just badly implement or just to generic in order to make it right (the rules engine gives me exactly this feeling). -aj I think you need to consider several factors in your evaluation of MailMate. I'm not saying it's for you, because it's certainly not for everyone. MailMate is a truly unique application. It is developed singlehandedly. The developer allows you to submit bug reports, converse with them frankly and directly about your issues, and even request features. Before continuing, you must at least acknowledge that an ungodly amount of effort has gone into making you and all of us happy with MailMate. If it's not clear to you already that being able to converse publicly and directly with a developer is unique in proprietary software, it should be now. Furthermore, MailMate offers classes of features that are unavailable in other mail clients, and even the ability to request more of these features and amendments to these features directly with a prompt and polite response. The bugs you have pointed out are non-obvious at best and edge cases at worst. For a single developer the fact that it works at all is quite impressive, especially in such an archaic language as Objective-C. I'm sure you realize that. You don't have the right to complain about bugs in software you do not own. If it really peeved you that your trial had so many bugs, you could have simply said here's why I'm not buying and moved on. Instead, you chose to write a screed decrying all Mac email clients, saying that they were all bad and the only difference between them was the price. Why you sent this to the MailMate public list, I'll never know. If you're sick of native mail clients, go use Gmail. It's a nice, sterile web service where I can assure you there will be no noticeable bugs and also nobody to talk to should you need help. Don't come whining to a single indie developer's mailing list about how much their and everyone else's product sucks. It adds literally nothing to the conversation and makes you look bad. Sincerely, Ben Klebe signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Dispatch for iPhone and MailMate
On 15 May 2015, at 21:26, Ben Klebe wrote: Any ideas for workarounds that solve this? And within 15 minutes I've solved my own problem. Sorry for wasting everyone's time. For the record what I did was setup a Gmail filter that labeled all incoming messages with the special MailMate archive label and the issue has been fixed. Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Dispatch for iPhone and MailMate
On 15 May 2015, at 22:00, Barton Lipman wrote: Interesting. Could you explain a bit more explicitly? Of course. So the problem I was having is that Dispatch is using what I assume to be a Google API to send messages to a folder/label named Archive. This folder is the default archive folder in Gmail. The result was that I could not search messages I had archived in Dispatch from MailMate when they had never been seen in MailMate. I setup a Gmail filter with the only criteria being that the message was sent to the open Gmail account and had the filter add MailMate's [Gmail]/Archive label. Problem solved. Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
[MlMt] Dispatch for iPhone and MailMate
I know MailMate uses a special Gmail label to fetch the archive, but for some reason whenever I use Dispatch to archive messages on my phone they don't get fetched on MailMate. Any ideas for workarounds that solve this? Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Customizing Bundles
I've changed them before. Just seeing if anyone else wanted it because I could also fork the repo, change it, then pull request the changes. ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Customizing Bundles
Hi all, While we're discussing OmniFocus, is it possible to get a discrete keyboard shortcut from the Evernote ones? Should I pull request the git repo with suggested changes? ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
[MlMt] Accidental Label Deletion
I was cleaning out a Gmail account from the web client and stupidly deleted the [Gmail]/Archive label that is placed there automatically by MailMate. Any suggestions for what I should do to fix this? I already tried replacing it and it doesn't seem to have helped. Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
Re: [MlMt] Accidental Label Deletion
On 12 Apr 2015, at 20:35, Ben Klebe wrote: I was cleaning out a Gmail account from the web client and stupidly deleted the [Gmail]/Archive label that is placed there automatically by MailMate. Any suggestions for what I should do to fix this? I already tried replacing it and it doesn't seem to have helped. Sincerely, Ben Klebe ___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate Never mind I restarted MailMate and it is fixed. Sorry to bother you with pointless blathering. Sincerely, Ben Klebe___ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
