On 2021-08-13, Cameron Simpson wrote:
> On 13Aug2021 08:17, Chris Green wrote:
>>On Fri, Aug 13, 2021 at 08:15:26AM +0200, Alexander Dahl wrote:
>>> On Thu, Aug 12, 2021 at 08:30:11AM +0100, Chris Green wrote:
>>> > I read my mail (via ssh) on quite a variety of devices, one is an
>>> > Android p
On 2021-07-21, isdtor wrote:
> I realize my config has a lot of moving parts and non-default
> settings, but I still hope someone can shine a light on this.
>
> I use less instead of the internal pager (note -R option),
>
> set pager="less -eiMR"
>
> and elinks for html display
>
> text/html; /usr
On 2020-08-12, Marcelo Laia wrote:
> On 12/08/20 at 11:18, Nuno Silva wrote:
>>
>> ls -l /home/myuser/.oauth2token
>>
>
>
> myuser@myuser:~$ ls -l /home/myuser/.oauth2token
> -rwxr-xr-x 1 myuser myuser 1957 ago 11 21:58 /home/myuser/.oauth2token
> myuser@myuser:~$
>
> myuser@myuser:~$ ls -
On 2020-08-12, Marcelo Laia wrote:
[...]
>
> My msmtprc is like this:
>
> account YZYZYZ
> host smtp.gmail.com
> from mylo...@yzyzyz.edu.br
> port 587
> protocol smtp
> tls on
> tls_trust_file /etc/ssl/certs/ca-certificates.crt
> auth oauthbearer
> user mylo...@yzyzyz.edu.br
> passwordeval /home/m
On 2019-10-29, martin f krafft wrote:
[...]
> Society has moved on, and we all risk sounding like grumpy old folks
> reminiscing at the times when everyone knew what netiquette was if we
> don't embrace the progress that's been happening around us. And
> text/html is part of that progress, whether
On 2019-10-29, John Long wrote:
> On Tue, 29 Oct 2019 14:50:05 -0400
> Patrick Shanahan wrote:
>
>> * Grant Edwards [10-29-19 13:10]:
[...]
>> > Muttdown (a "sendmail" filter) which creates mutlipart alternative
>> > html/text messages is the only reason I've been able to continue to
>> > use mu
On 2019-10-21, Chris Green wrote:
> On Sun, Oct 20, 2019 at 05:08:01PM -0400, Nathan Stratton Treadway wrote:
>> On Sun, Oct 20, 2019 at 18:04:05 +0100, Chris Green wrote:
>> > I just removed apparmor from one of my systems (I can see no use for
>> > it anyway), I still get the error with evince.
On 2019-10-20, Marcelo Laia wrote:
> On 20/10/19 at 02:02, Nuno Silva wrote:
>
>> Do these systems have apparmor? It seems to be some sort of security
>> tool which restricts access to files and directories based on rules.
>
>
> Bingo
>
> root@marcelo:~# dpkg -l apparmor
> Desired=Unknown/In
On 2019-10-20, José María Mateos wrote:
> On Sun, 20 Oct 2019 10:15:34 -0300 Marcelo Laia
> wrote:
>> root@marcelo:~# dpkg -l apparmor
>> Desired=Unknown/Install/Remove/Purge/Hold
>> |
>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-require
On 2019-10-20, Chris Green wrote:
> On Sun, Oct 20, 2019 at 11:01:02AM +0200, Matthias Apitz wrote:
>> El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva
>> escribió:
>>
>> > On 2019-10-19, José María Mateos wrote:
>> >
>> > > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green
On 2019-10-19, José María Mateos wrote:
> On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
>> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
>> but running 'evince ~/.mutt/fred.pdf' produces a Permission Denied
>> message in a pop-up window. All directory names I have
On 2019-01-30, Marcelo Laia wrote:
> Dear,
>
> I will try to clarify with a video.
>
> Please, could you see it here?
>
> https://www.dropbox.com/s/61sb07hx4stvbcs/mutt-file-not-open.mp4?dl=0
>
> In this video, I did:
>
> Opem mutt, go to message, open the attach view, hint the attach file.
>
> Af
On 2018-12-13, Derek Martin wrote:
> On Wed, Dec 12, 2018 at 01:18:04PM +1100, Erik Christiansen wrote:
>
>> Then the thoughts of the majority of the community bear
>> consideration, especially when based on reason.
>
> The majority of the community said nothing at all, which suggests (as
> I sug
On 2018-12-11, Derek Martin wrote:
> On Tue, Dec 11, 2018 at 08:39:31PM +1100, Erik Christiansen wrote:
>> On 10.12.18 17:29, Derek Martin wrote:
>> >When a message is a reply to another message, the mailboxes of the
>> >authors of the original message (the mailboxes in the "From:"
>> >
On 2018-10-25, Derek Martin wrote:
> On Thu, Oct 25, 2018 at 11:11:52AM -0500, Derek Martin wrote:
>> On Thu, Oct 25, 2018 at 12:53:43PM +0100, Nuno Silva wrote:
>> > When I use emacsclient, the interface locale is not broken: the terminal
>> > I/O encoding is correctly set from the locale. The on
On 2018-10-24, Derek Martin wrote:
> On Tue, Oct 23, 2018 at 10:31:45PM +0100, Nuno Silva wrote:
>> On 2017-10-12, nunojsi...@ist.utl.pt wrote:
>>
>> > Recently, I have tried to use mutt on a non-utf8 terminal. Everything
>> > works as expected in an utf8 environment, but when I compose new e-ma
On 2018-10-24, Ian Zimmerman wrote:
> On 2018-10-23 22:31, Nuno Silva wrote:
>
>> So far I did not find a way to change this on the mutt side, but I made
>> a new major mode for mutt messages in Emacs (the editor I use with
>> mutt), with a hook that changes the file encoding to latin1 if the file
On 2017-10-12, nunojsi...@ist.utl.pt wrote:
> Recently, I have tried to use mutt on a non-utf8 terminal. Everything
> works as expected in an utf8 environment, but when I compose new e-mails
> in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
> same encoding as the terminal,
On 2018-08-30, nunojsi...@ist.utl.pt wrote:
> I've been sending GPG-encrypted e-mails with mutt, and I've noticed that
> the key ID selection menu, the one that shows up when there is more than
> one identity in a given recipient's key, is a bit too long for 80
> columns.
>
> This means that, when
On 2018-03-12, Kevin J. McCarthy wrote:
> The new mailing list server uses GNU mailman. There are likely a few
> things that need to be tweeked. Please let me know about any issues.
I only noticed this now. As far as I can tell, it hasn't been mentioned
here yet: (I might have overlooked some m
I've been sending GPG-encrypted e-mails with mutt, and I've noticed that
the key ID selection menu, the one that shows up when there is more than
one identity in a given recipient's key, is a bit too long for 80
columns.
This means that, when I send encrypted e-mails from an 80-column
terminal, at
On 2018-03-12, Kevin J. McCarthy wrote:
> On Mon, Mar 12, 2018 at 10:01:08PM +, Nuno Silva wrote:
>> It looks like the "nomail" subscription setting was lost in this
>> transition.
>>
>> I have been subscribed that way for some time and today, for the first
>> time ever, I received a few emai
On 2018-03-12, Kevin J. McCarthy wrote:
> Last Friday night, our mailing list and website server suffered a
> catastrophic failure.
>
> Fortunately, for the past couple months I have already been working on
> moving our mailing lists to OSUOSL. I had planned a couple more steps
> to transition sm
Hello,
Recently, I have tried to use mutt on a non-utf8 terminal. Everything
works as expected in an utf8 environment, but when I compose new e-mails
in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
same encoding as the terminal, while my text editor will save the file
in u
24 matches
Mail list logo
