python wrapper script.
(1) https://github.com/stevekm/mutt-py
Cheers,
felixs
On Thu, Apr 18, 2019 at 09:16:55AM +1000, Cameron Simpson wrote:
> On 17Apr2019 22:45, felixs wrote:
> > Thanks for your detailed comments and explanations. It will need a
> > second lecture with the Bash Reference Manual opened in another terminal
> > to fully under
essage in order to reply to
you maintaing the threading; I hope it works.
Thanks
felixs
Thanks for your detailed comments and explanations. It will need a
second lecture with the Bash Reference Manual opened in another terminal
to fully understand the differences.
felixs
On Wed, Apr 17, 2019 at 08:28:56AM +1000, Cameron Simpson wrote:
> On 16Apr2019 18:40, felixs wrote:
> &g
On Tue, Apr 16, 2019 at 09:52:57AM +1000, Cameron Simpson wrote:
> On 15Apr2019 11:23, felixs wrote:
> > Thanks, Cameron. Some coments go in between your comments.
>
> As they should :-)
>
> > > If you go:
> > >
> > > sed ... > >
> >
Thanks, Derek.
On Mon, Apr 15, 2019 at 12:02:18PM -0500, Derek Martin wrote:
> On Sun, Apr 14, 2019 at 08:06:04PM +0200, felixs wrote:
> > I searched in the documentation of sed (info sed), the bash-hacker's
> > wiki (1) and read through the Advanced Bash Scripting Guide, but I
&g
On Mon, Apr 15, 2019 at 01:13:05PM +0200, Francesco Ariis wrote:
> On Mon, Apr 15, 2019 at 11:33:45AM +0200, felixs wrote:
> > Please see UPDATE section
> > [...]
>
> Hello everyone,
> the `In-Reply-To` header for this discussion keeps getting mangled,
> which confu
Please see UPDATE section
- Forwarded message from felixs -
Date: Mon, 15 Apr 2019 11:23:29 +0200
From: felixs
To: mutt-users@mutt.org
Subject: Re: [Fwd: Re: Send to a Listing]
Thanks, Cameron. Some coments go in between your comments.
On Mon, Apr 15, 2019 at 05:15:37PM +1000
Thanks, Cameron. Some coments go in between your comments.
On Mon, Apr 15, 2019 at 05:15:37PM +1000, Cameron Simpson wrote:
> On 15Apr2019 08:52, felixs wrote:
> > > However, sed can instead accept a list of files on the command line
>
> Which felixs has t
On Mon, Apr 15, 2019 at 05:10:14PM +1000, Cameron Simpson wrote:
> On 15Apr2019 08:34, felixs wrote:
> > On Mon, Apr 15, 2019 at 07:33:53AM +1000, Cameron Simpson wrote:
> > > On 15Apr2019 07:19, Cameron Simpson wrote:
> > > > Think about it. You're invoking sed _
:
> On Sun, Apr 14, 2019 at 20:06:04 +0200, felixs wrote:
> > sed -ne '/^From: $EMAIL_ADDRESS/p ; /Subject: $SUBJECT/p' \
> > < /path/to/spoolfile
> >
> > If I specify a message file on the command line it works. If I try to
> > make sed take its input from
_ALL=C). May this be a bash i18n bug (a somewhat strange bug),
a bash packaging bug of my distribution, I'm not sure where to send a
bug report to. And the fact that bash (when invoking sed) does not accept
< /path/* in itself is worth a bug report.
Cheers,
felixs
I have placed my comments among yours, I hope you don't mind.
On Mon, Apr 15, 2019 at 07:19:14AM +1000, Cameron Simpson wrote:
> On 14Apr2019 20:06, felixs wrote:
> > fiddling with sed in the mutt mailing bash script
>
> Nothing you're doing requires bash. Just use /bin/
ame variable it always expands to a
directory or to a given file, but to all the files of a directory?
Any suggestions appreciated.
felixs
(1) https://wiki.bash-hackers.org/syntax/redirection
- Forwarded message from felixs -
Date: Fri, 12 Apr 2019 00:19:52 +0200
From: felixs
To: Willem O
On Thu, Apr 11, 2019 at 07:12:57PM -0500, Derek Martin wrote:
> On Sun, Apr 07, 2019 at 11:13:53PM +0200, felixs wrote:
> > On Fri, Apr 05, 2019 at 11:24:26AM -0700, Ian Zimmerman wrote:
> > > I think this is the first time I got hit by the next stage of
> > > browse
testing with my cloud account.
I will keep you and the list informed.
felixs
- End forwarded message -
Just to follow up: I have been trying to use glcoud (SDK) to get access to
my cloud account (for doing a mutt-related project),
but connecting via console I always get an oauth2 url
link
n not to go
for XOAUTH2 SASL. I hadn't read the RFC, just the Google page related to
their XOAUTH2 (Gmail API pages, don't have the link here), which on the
other hand might be outdated by now.
I'm still struggling a bit with Google's OAUTH2 implementation, but
that'll be the subject of another message which I promised to a certain
list member.
felixs
>
into the
addresses_file.txt, and to modify it inserting commas, so that the file
may be further processed by mutt. But that's just an idea.
I will take up the crontab suggestion. Thanks for all.
felixs
On Thu, Apr 11, 2019 at 08:13:13PM +0200, Willem Offermans wrote:
> Dear Felixs and mutt friends,
>
Thanks for your reply.
On Wed, Apr 10, 2019 at 08:50:53AM +0200, Willem Offermans wrote:
> Dear Felixs and mutt friends,
>
> FreeBSD with mutt, that is a strong team :)
I'm about to try using this strong team, my FreeBSD installation medium is still
on my table. Hearing you here clap
lare a variable in a shell script script.sh
addresses=address1, address2, address3
mutt -s "YOUR SUBJECT" $addresses
Let me know if that worked for you on FreeBSD. And don't tell me
anything if it does not ;-)
Cheers,
felixs
On Tue, Apr 09, 2019 at 05:32:41PM -0500, Software Info wrote:
> HI
d later like to write a
> script to include this command later on.
>
>
> Regards
> SoftInfoJ
>
> Sent from Mail for Windows 10
For Linux or for Windows?
On which platform are you using mutt?
Cheers,
felixs
On Mon, Apr 08, 2019 at 08:40:09PM -0700, Ian Zimmerman wrote:
> On 2019-04-07 23:13, felixs wrote:
>
> > > From: "Foo Bari"
> > >
> > > where the entity refers to the character U0107 in Unicode code point
> > > space. I would like to aut
On Mon, Apr 08, 2019 at 08:40:09PM -0700, Ian Zimmerman wrote:
> On 2019-04-07 23:13, felixs wrote:
>
> > > From: "Foo Bari"
> > >
> > > where the entity refers to the character U0107 in Unicode code point
> > > space. I would like to aut
.
And if you add
set charset="utf-8"
to your muttrc conf file?
Cheers,
felixs
- Forwarded message from felixs -
Date: Sun, 31 Mar 2019 20:14:30 +0200
From: felixs
To: Todd Zullinger
Cc: mutt-users@mutt.org
Subject: [Fwd: Re: Patch [was Re: [Fwd: Re: Impossible to connect to mail
server via pops3 using mutt 1.11]]
- Forwarded message from felixs
- Forwarded message from felixs -
Date: Sat, 30 Mar 2019 23:52:02 +0100
From: felixs
To: Todd Zullinger
Cc: mutt-users@mutt.org
Subject: Re: Patch [was Re: [Fwd: Re: Impossible to connect to mail server via
pops3 using mutt 1.11]
On Fri, Mar 29, 2019 at 03:35:28PM -0400, Todd
- Forwarded message from felixs -
On Fri, Mar 29, 2019 at 03:43:11PM -0700, Kevin J. McCarthy wrote:
> On Fri, Mar 29, 2019 at 07:57:49PM +0100, felixs wrote:
> > OK, I managed to apply the patch as an email patchfile using
> >
> > git am /path/to/patch
> >
On Fri, Mar 29, 2019 at 03:35:28PM -0400, Todd Zullinger wrote:
> Hi,
>
> felixs wrote:
> > On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote:
> >> On Thu, Mar 28, 2019 at 10:20:54PM +0100, felixs wrote:
> >>> I tried to access the b
On Sat, Mar 30, 2019 at 09:07:24AM +1100, Cameron Simpson wrote:
> On 29Mar2019 13:05, felixs wrote:
> > On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote:
> > > On 28Mar2019 22:20, felixs wrote:
> > > > I tried to access the branch
On Fri, Mar 29, 2019 at 08:57:36AM -0700, Kevin J. McCarthy wrote:
> On Fri, Mar 29, 2019 at 12:48:46PM +0100, felixs wrote:
> > On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote:
> > > The repo is clonable via <https://gitlab.com/muttmua/mutt.git>,
> &g
On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote:
> On 28Mar2019 22:20, felixs wrote:
> > I tried to access the branch with the patch, but the access is
> > password-protected. Are you able to share the patchfile by other means?
> > Signing up with gitlab is an
On Thu, Mar 28, 2019 at 03:11:34PM -0700, Kevin J. McCarthy wrote:
> On Thu, Mar 28, 2019 at 10:20:54PM +0100, felixs wrote:
> > I tried to access the branch with the patch, but the access is
> > password-protected.
>
> The repo is clonable via <https://gitlab.com/mutt
g with my cloud account.
I will keep you and the list informed.
felixs
>
On Wed, Mar 27, 2019 at 09:18:22AM -0700, Kevin J. McCarthy wrote:
> On Wed, Mar 27, 2019 at 04:54:04PM +0100, felixs wrote:
> > Having studied oauth2 more in depth I do not consider it to be secure
> > enough (as such) mainly because of its overwhelming complexity, and I wi
On Wed, Mar 27, 2019 at 09:18:22AM -0700, Kevin J. McCarthy wrote:
> On Wed, Mar 27, 2019 at 04:54:04PM +0100, felixs wrote:
> > Having studied oauth2 more in depth I do not consider it to be secure
> > enough (as such) mainly because of its overwhelming complexity, and I wi
On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote:
> On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote:
> > 'getoauthbearersupport' and 'no refresh command defined', not showing
> > any willingness to download my e-mais.
>
> Hi felixs,
>
>
Test
- Forwarded message from felixs -
Date: Sun, 24 Mar 2019 12:59:35 +0100
From: felixs
To: "Kevin J. McCarthy"
Cc: mutt-users@mutt.org
Subject: Re: Impossible to connect to mail server via pops3 using mutt 1.11
On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote
using v.1.11.3
(well, no, currently, I am using the web interface, for obvious
reasons)
So, is this a bug, or a feature to convince people to adopt oauth mechanism? ;-)
Any comment, help or pointer is appreciated.
felixs
39 matches
Mail list logo
