
On 11/02/2016 12:27 AM, Jason White via luv-talk wrote:
I am in a work environment that is heavily invested in it. The problem is that if the original message is in HTML, the reply is automatically also in HTML and the configuration option that prefixes each line with a > character doesn't take effect. Is there a straightforward solution to this? Switching the message to plain text after issuing the "reply" command doesn't help.
True, HTML really screws things up with Outlook. I used to work in an Outlook/Exchange environment, so I know what you're talking about.
Outlook is firmly part of the Microsoft tradition: large, complex, monolithic, a bug rate to match the impressive feature list, and crashes too often... but the features are nice and the integration of mail and calendar is very good. The keyboard commands are fairly comprehensive - I can't complain that my efficiency is reduced by a lack of keyboard operations (unlike Apple Mail, which I also use). Actually, Microsoft are very good at providing keyboard bindings for their graphical user interfaces - significantly superior to GNOME or Mozilla, disappointingly enough.
Yes, Microsoft have always been good at providing keyboard bindings for their OSs and applications.
Nothing is better for keyboard access than the UNIX text environment, including Emacs and Vi, the shell, etc. I'm using this environment quite extensively, with Pandoc's Markdown as my primary document format at the moment, and Git for revision control.
True, UNIX shells are best for keyboard use. I do have some requirements for mail interfaces that do favour well written graphical clients, though some text mode programs do work well for me. It's hard to quantify, and has a lot to do with how well the design of the software lines up with my internal intuitive logic. vi and Emacs haven't lined up particularly well (vi has been the slightly better of those two for me). I trued mutt and found similar issues where it didn't mesh well in a couple of key ways with how I work. I need something that either just "makes sense" (i.e. I can drive much of it without having to RTFM ;) ), or uses ancient commands that became ingrained when I had more time and more time in front of the editors (e.g. those ancient Wordstar/Borland editor commands). -- 73 de Tony VK3JED/VK3IRL http://vkradio.com