Re: Mailcap for .docx files (using docx2txt or similar)
On Fri, Jan 22, 2021 at 06:24:22PM +0530, Chinmaya Nagpal wrote: > On Fri, Jan 22, 2021 at 12:35:46PM +, Chris Green wrote: > > So, it would be handy to have mutt configured to use one to view .docx > > files. I'm sure somebody must have done this already so what does the > > ~/.mailcap entry have to look like? > > This works for pandoc: > application/vnd.openxmlformats-officedocument.wordprocessingml.document; > pandoc --from docx --to markdown %s; copiousoutput > Wonderful! I'd never come across pandoc before, it seems to be able to do almost anything! ... and it's maintained/up to date. Thank you. > Source: > https://raymii.org/s/articles/Viewing_PDF_docx_and_odt_files_in_Mutt.html -- Chris Green
Re: GMail SMTP: no authenticators available?
On Wed, Jan 20, 2021 at 16:22 -1000, Baron Fujimoto wrote: > Our og's email is hosted by Gmail (via GSuite). I had been using > neomutt (built from MacPorts) successfully for years. Maybe I can point you in some useful direction: I had exactly this problem with a self-built mutt recently after upgrading macOS and rebuilding all the ports (and mutt). It took me a while to find what was going on: MacPorts' libsasl2 seemed to have trouble with GMail. I uninstalled that and had mutt link against /usr/lib/libsasl2.2.dylib, and everything went back to working normally for me. Now, here's the funny thing: as I'm writing this, I just double checked my mutt binary. Turns out it's back to linking against MacPorts (now /opt/local/lib/libsasl2.3.dylib). I've rebuilt mutt in the meantime a couple of times, so things must have reverted. But it's all still working fine, which probably means that it was libsasl2 version thing somehow that's been corrected by now. Robin -- Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin
Re: Japanese characters?
> > by accident I discovered that I can compose Japanese kana (hiragana, > > katakana) in mutt. > > This sound like you have `:set digraph` in your vim editor (might be in > a filetype plugin or autocommand, so that is only applies to mails you > edit from mutt). Bingo! in my vimrc file I have the following lines containing `digraphs`, but forgot I put it in because I started to use just the keyboard for accented characters. " handle mutt mail replies better 18 autocmd BufNewFile,BufRead /tmp/mutt* set noautoindent filetype=mail wm=0 tw=78 nonumber digraph nolist 19 autocmd BufNewFile,BufRead ~/tmp/mutt* set noautoindent filetype=mail wm=0 tw=78 nonumber digraph nolist TNX! //meine
Re: Mailcap for .docx files (using docx2txt or similar)
> This works for pandoc: > application/vnd.openxmlformats-officedocument.wordprocessingml.document; > pandoc --from docx --to markdown %s; copiousoutput > > Source: > https://raymii.org/s/articles/Viewing_PDF_docx_and_odt_files_in_Mutt.html Thanks for this! not only makes this work in mutt, but could also be used fore a rule how to handle those filetypes in a file manager, without the need for the application itself. //meine
Re: Mailcap for .docx files (using docx2txt or similar)
> So, it would be handy to have mutt configured to use one to view .docx > files. I'm sure somebody must have done this already so what does the > ~/.mailcap entry have to look like? in my .mutt/mailcap (FreeBSD) application/ms-word; catdoc %s //meine
Re: Mailcap for .docx files (using docx2txt or similar)
On Fri, Jan 22, 2021 at 12:35:46PM +, Chris Green wrote: > So, it would be handy to have mutt configured to use one to view .docx > files. I'm sure somebody must have done this already so what does the > ~/.mailcap entry have to look like? This works for pandoc: application/vnd.openxmlformats-officedocument.wordprocessingml.document; pandoc --from docx --to markdown %s; copiousoutput Source: https://raymii.org/s/articles/Viewing_PDF_docx_and_odt_files_in_Mutt.html
Mailcap for .docx files (using docx2txt or similar)
I just saw a note from someone on a Linux list asking about simple programs to convert .docx files to text. It turns out that there are several docx2txt programs out there. So, it would be handy to have mutt configured to use one to view .docx files. I'm sure somebody must have done this already so what does the ~/.mailcap entry have to look like? -- Chris Green
Re: Japanese characters?
On Do, 21 Jan 2021, meine wrote: > hi, > > by accident I discovered that I can compose Japanese kana (hiragana, > katakana) in mutt. I wonder if this is a feature, or somewhere lurking > in my mutt and FreeBSD setup (although I only use default software and > settings). I have NL language settings for UTF-8 on a user level in my > system, and use Vim as the editor for my emails. BTW, this described > here doesn't work in Vim, but only in mutt. > > It works like this: > > typing a letter, then backspace and then another letter -- just making a > typo and correcting it. > > m e --> め (hiragana `me`) > > M e -- メ (katakana `me`) > > it just works with all characters, only the plain `a` in both writings I > cannot find. > > this way of composing also gives acces to Cyrillic `ja` я, ju `ю` and > `cs` щ, and also to e.g. Arabic numbers ۰ ۱ ۲ ۳ ۴ ۵ ۶ ۷ ۸ and ۹ by > combining a number and `a` as described above. > > this way of composing is different from typing characters that are > behind the or right-alt key, which I use for typing several > European languages (å ä é ø æ ü, etc). > > somehow it is funny to be able to write my name in Japanese, but it can > also be a PITA when making too much typo's. so my question is: > > * is this a feature of mutt? > > * can it be switched on/off somehow? This sound like you have `:set digraph` in your vim editor (might be in a filetype plugin or autocommand, so that is only applies to mails you edit from mutt). regards, Christian -- There will be big changes for you but you will be happy.
Re: Japanese characters?
On Thu, Jan 21, 2021 at 10:11:27PM +0100, meine wrote: > > by accident I discovered that I can compose Japanese kana (hiragana, > katakana) in mutt. I wonder if this is a feature, or somewhere lurking > in my mutt and FreeBSD setup (although I only use default software and > settings). I have NL language settings for UTF-8 on a user level in my > system, and use Vim as the editor for my emails. BTW, this described > here doesn't work in Vim, but only in mutt. I'm using mutt and compose Japanese text with emacs. but mutt is not original, Japanese patch applied. (https://ja.osdn.net/projects/mutt-j/) > > It works like this: > > typing a letter, then backspace and then another letter -- just making a > typo and correcting it. > > m e --> め (hiragana `me`) > > M e -- メ (katakana `me`) > > it just works with all characters, only the plain `a` in both writings I > cannot find. Does this behavior occur in mutt's builtin editor, or does it occur in vim?
