Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-22 Thread Benny Kjær Nielsen 

On 21 Dec 2016, at 21:44, Charlie Garrison wrote:


On 22 Dec 2016, at 0:08, Verdon Vaillancourt wrote:


Sorry for any confusion I have caused,


I don’t think you caused any confusion.  ;-)


I think I caused the confusion by not escaping characters correctly when 
I wanted to recommend dash-dash-space.


I jumped in since I was having a similar problem, but my issue was 
‘lack’ of formatting unless I introduce a blank line. I would like 
for my sig content to be on the following line from the sig marker, 
not with a blank line between sig marker and sig content.


Benny, I gave an example in an earlier message in this thread. Would 
it be helpful if I sent a proper report to feedback address.


This is probably unlikely to change. It would mean that dash-dash-space 
needed to be treated differently than, e.g., a line with some text.


In any case, my plan is to switch the default Markdown converter to 
something else. I currently use a 
[modified](https://github.com/freron/upskirt) version of `sundown`.


--
Benny
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-21 Thread Charlie Garrison 

On 22 Dec 2016, at 0:08, Verdon Vaillancourt wrote:


Sorry for any confusion I have caused,


I don’t think you caused any confusion.  ;-)

I jumped in since I was having a similar problem, but my issue was 
‘lack’ of formatting unless I introduce a blank line. I would like 
for my sig content to be on the following line from the sig marker, not 
with a blank line between sig marker and sig content.


Benny, I gave an example in an earlier message in this thread. Would it 
be helpful if I sent a proper report to feedback address.


cng

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-21 Thread Sam Hathaway 

On 12/21/2016 8:08 am, Verdon Vaillancourt wrote:


In the end, I think mail mate is likely behaving as it should, and I
didn’t understand that the sig marker required a  after the
dashes.

Sorry for any confusion I have caused,


No worries! Thanks for the explanation.
-sam

___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-21 Thread Verdon Vaillancourt 
I think my original question/observation has become lost in the thread, 
and I may not have phrased my last remark well.


Initially, my sig marker was just  and what that caused was 
my closing salutation to be made into a header by the markdown 
processor, e.g..


best wishes
--
Verdon Vaillancourt


I have since been informed, and then verified that using 
 OR  as my sig marker, leads to 
the markdown processor ignoring the sig marker, and not treating it as 
if it was a header indicator, e.g..


best wishes
--
Verdon Vaillancourt

In the end, I think mail mate is likely behaving as it should, and I 
didn’t understand that the sig marker required a  after the 
dashes.


Sorry for any confusion I have caused,

v




On 20 Dec 2016, at 19:48, Charlie Garrison wrote:


On 21 Dec 2016, at 10:41, Sam Hathaway wrote:

But, "dash dash space" *is* the proper sig marker, right? As (I 
think) we covered earlier in this thread? Does MailMate fall down on 
"dash dash space"?


I haven’t tested with different sig markers, but Verdon said:

Introducing the space on either end leads to the  being 
ignored by the markdown processor


I read that to mean that MailMate fails with dash,dash,space.

And yes, reading the Usenet RFC, dash,dash,space,newline is correct 
sig marker.


cng

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)




___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-20 Thread Charlie Garrison 

On 21 Dec 2016, at 10:41, Sam Hathaway wrote:

But, "dash dash space" *is* the proper sig marker, right? As (I think) 
we covered earlier in this thread? Does MailMate fall down on "dash 
dash space"?


I haven’t tested with different sig markers, but Verdon said:

Introducing the space on either end leads to the  being 
ignored by the markdown processor


I read that to mean that MailMate fails with dash,dash,space.

And yes, reading the Usenet RFC, dash,dash,space,newline is correct sig 
marker.


cng

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-20 Thread Sam Hathaway 
On December 20, 2016 3:38:16 PM EST, Charlie Garrison 
 wrote:

> can you fix it so it handles proper sig markers?

But, "dash dash space" *is* the proper sig marker, right? As (I think) we 
covered earlier in this thread? Does MailMate fall down on "dash dash space"?
-sam
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-20 Thread Charlie Garrison 

On 21 Dec 2016, at 0:42, Verdon Vaillancourt wrote:

Introducing the space on either end leads to the 
dashdash being ignored by the markdown processor


Hmm, the markdown processor needs a cluestick.

Benny, how much control do you have over the markdown processor, can you 
fix it so it handles proper sig markers?


cng

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-19 Thread Charlie Garrison 

On 20 Dec 2016, at 7:51, Verdon Vaillancourt wrote:

I found that spacedashdash worked for me… I 
think ;-)


Unless given good reason otherwise, I’ll stay with the spec (RFC) for 
now.


- https://tools.ietf.org/html/rfc3676#section-4.3

Or for unofficial but easier to read:

- https://en.wikipedia.org/wiki/Signature_block (“Signatures in Usenet 
postings” section)


Yes, the references were originally for Usenet before being adopted by 
email.


I’ve been using dash,dash,space for 20 years; I’ll need a compelling 
reason before I switch. ;-)


--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-19 Thread Verdon Vaillancourt 

I found that  worked for me… I think ;-)


On 19 Dec 2016, at 15:49, Charlie Garrison wrote:


On 19 Dec 2016, at 23:42, Benny Kjær Nielsen wrote:


On 14 Dec 2016, at 21:39, Charlie Garrison wrote:

Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


I do give it special treatment, but only to `--` and not `--`. 
Note the added space.


I can’t tell which variant has the extra space in your example. 
According to specs, the signature marker should be  
which is what I use for my sigs.


If you’re saying that dash,dash,space gets special treatment 
already, then maybe there is a bug. Compare the two sigs below, both 
with dash,dash,space sig marker, and are identical except for blank 
line after sig marker (I removed blank line from first one).


--
Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-19 Thread Charlie Garrison 

On 19 Dec 2016, at 23:42, Benny Kjær Nielsen wrote:


On 14 Dec 2016, at 21:39, Charlie Garrison wrote:

Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


I do give it special treatment, but only to `--` and not `--`. Note 
the added space.


I can’t tell which variant has the extra space in your example. 
According to specs, the signature marker should be  
which is what I use for my sigs.


If you’re saying that dash,dash,space gets special treatment already, 
then maybe there is a bug. Compare the two sigs below, both with 
dash,dash,space sig marker, and are identical except for blank line 
after sig marker (I removed blank line from first one).


--
Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)

--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-19 Thread Verdon Vaillancourt 

Good to know! :-)

On 19 Dec 2016, at 7:42, Benny Kjær Nielsen wrote:


On 14 Dec 2016, at 21:39, Charlie Garrison wrote:

Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


I do give it special treatment, but only to `-- ` and not `--`. Note 
the added space.


--
Benny
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-19 Thread Benny Kjær Nielsen 

On 14 Dec 2016, at 21:39, Charlie Garrison wrote:

Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


I do give it special treatment, but only to `-- ` and not `--`. Note the 
added space.


--
Benny
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-14 Thread Verdon Vaillancourt 

a… Thank you! I will play.

v


On 14 Dec 2016, at 15:39, Charlie Garrison wrote:


On 15 Dec 2016, at 7:25, Verdon Vaillancourt wrote:

… my email auto-formats the closing line as something big and bold, 
and I now have a formatted email instead of a simple plain text, 
which is completely unnecessary in most cases.


Is there some preference I am missing that will stop that behaviour?


It’s the Markdown header formatting. Put a blank line between the 
dashes and the signature content.


Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


Charlie

PS. Note the blank line in my sig; the markdown formatting breaks 
without that blank line.


--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Re: [MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-14 Thread Charlie Garrison 

On 15 Dec 2016, at 7:25, Verdon Vaillancourt wrote:

… my email auto-formats the closing line as something big and bold, 
and I now have a formatted email instead of a simple plain text, which 
is completely unnecessary in most cases.


Is there some preference I am missing that will stop that behaviour?


It’s the Markdown header formatting. Put a blank line between the 
dashes and the signature content.


Feature request: Give special treatment to the signature marker so 
it’s not interpreted as Markdown formatting.


Charlie

PS. Note the blank line in my sig; the markdown formatting breaks 
without that blank line.


--

Charlie Garrison   
Garrison Computer Services  
PO Box 380
Tumbarumba NSW 2653  Australia

[Conundrum](http://www.ietf.org/rfc/rfc1855.txt)
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

[MlMt] Triggering markdown with 'complimentary close' above signature

2016-12-14 Thread Verdon Vaillancourt 

Hi,

Apologies if this is covered in the help, and I am missing it.

I prefer email I am sending to be in plain text whenever possible. 
Occasionally formatted text is needed, so I have not completely disabled 
html or markdown. By default, all mail I am composing starts as plain 
txt. In the case where a signature is being added, and the signature is 
like the following, staring with two dashes…


--
Verdon Vaillancourt


… as soon as I add a closing line above the signature, e.g..

Best regards,

… my email auto-formats the closing line as something big and bold, 
and I now have a formatted email instead of a simple plain text, which 
is completely unnecessary in most cases.


Is there some preference I am missing that will stop that behaviour?

Best wishes,
verdon
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate