Pentadactyl and gmail's new compose experience

96 views
Skip to first unread message

Alexandre Provencio

unread,
Mar 29, 2013, 3:06:33 PM3/29/13
to penta...@googlegroups.com
Hello guys, I have been using penta's i_C-i on gmail's compose area to
edit my emails within a beautiful gvim window, with easy quoting of
older emails, syntax highlighting and all the cool things we all know.
The only gotcha was to have the email set as plain text and everything
went fine.

Now gmail is pushing us (for good) this new compose experience which
brings me problems to achieve my usual workflow: First I always have to
activate the '...' button in order to see older emails but the worst
thing is that even marking the email as plain text I still get a lot of
html tags when going to the gvim window which messes syntax highlighting
and everything else.

Is there something that can be done on Penta's side? Do you think gmail
team can do anything about it? Is it a good time for me getting a real
MUA (i.e. TB+Teledactyl, Mutt)?

- Alexandre

Nick Harding

unread,
Apr 1, 2013, 9:32:08 AM4/1/13
to penta...@googlegroups.com
Sorry- can't help with your problem, but I'm very interested about the gvim interface you describe! Is there a wiki/guide anywhere? Thanks!

Alexandre Provencio

unread,
Apr 2, 2013, 10:27:28 AM4/2/13
to penta...@googlegroups.com
On Mon, Apr 1, 2013 at 10:32 AM, Nick Harding <nickh...@gmail.com> wrote:
> Sorry- can't help with your problem, but I'm very interested about the gvim
> interface you describe! Is there a wiki/guide anywhere? Thanks!
Hello Nick, nothing special, on pentadactylrc there is:
:au LocationChange !mail.google.com,* :set editor&
:au LocationChange 'mail.google.com' :set editor="gvim -f -c 'set
ft=mail' +<line>"

- Alexandre

>
>
> On Friday, 29 March 2013 15:06:33 UTC-4, Alexandre Provencio wrote:
>>
>> Hello guys, I have been using penta's i_C-i on gmail's compose area to
>> edit my emails within a beautiful gvim window, with easy quoting of
>> older emails, syntax highlighting and all the cool things we all know.
>> The only gotcha was to have the email set as plain text and everything
>> went fine.
>>
>> Now gmail is pushing us (for good) this new compose experience which
>> brings me problems to achieve my usual workflow: First I always have to
>> activate the '...' button in order to see older emails but the worst
>> thing is that even marking the email as plain text I still get a lot of
>> html tags when going to the gvim window which messes syntax highlighting
>> and everything else.
>>
>> Is there something that can be done on Penta's side? Do you think gmail
>> team can do anything about it? Is it a good time for me getting a real
>> MUA (i.e. TB+Teledactyl, Mutt)?
>>
>> - Alexandre
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Pentadactyl" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pentadactyl...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Reply all
Reply to author
Forward
0 new messages