Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

The pylint message about an undefined variable was mistaken because that 
variable can only be used after the condition has been met.  Tested to 
confirm.

I have created a PR for this updated version.

Unless someone reports anything seriously wrong or trivial to fix in the 
next few days, I will release it as a non-beta release.  In the meantime, 
this version is V3.0b15.

On Thursday, September 3, 2020 at 11:08:04 AM UTC-4, Thomas Passin wrote:
>
>
> On Thursday, September 3, 2020 at 10:59:41 AM UTC-4, Edward K. Ream wrote:
>>
>>
>>> Actually, I knew about it.  I'm not sure if it's real or something that 
>>> pylint doesn't understand (I think it's this). 
>>>
>>
>> If it's a pylint mistake, please disable the message.
>>
>
>  I will once I'm sure.  I purposely have not disabled the message until 
> I'm convinced it's spurious.
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/d7c1cd03-a40a-4ef1-bfb7-4731bfd9100eo%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

On Thursday, September 3, 2020 at 10:59:41 AM UTC-4, Edward K. Ream wrote:
>
>
>> Actually, I knew about it.  I'm not sure if it's real or something that 
>> pylint doesn't understand (I think it's this). 
>>
>
> If it's a pylint mistake, please disable the message.
>

 I will once I'm sure.  I purposely have not disabled the message until I'm 
convinced it's spurious.

>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ecedbee4-c1df-4e2d-8cee-1533cb54b8dao%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Edward K. Ream]

On Thu, Sep 3, 2020 at 7:30 AM Thomas Passin  wrote:

>
> pylint gives this complaint:
>>
>> * Module leo.plugins.viewrendered3
>> leo\plugins\viewrendered3.py:1803:23: E0602: Undefined variable
>> 'AsciiDocError' (undefined-variable)
>>
>> Do you get the same complaint? If so, please attempt to remove it.
>> Thanks.
>>
>
> Actually, I knew about it.  I'm not sure if it's real or something that
> pylint doesn't understand (I think it's this).
>

If it's a pylint mistake, please disable the message.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0sQKh5Kvk-CREaiw6BEEsGmDkmeVWcT1KNGoO%2BRfE0ew%40mail.gmail.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

On Thursday, September 3, 2020 at 7:20:39 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Wednesday, September 2, 2020 at 10:30:08 PM UTC-5, Thomas Passin wrote:
>>
>> I've just submitted a pull request for viewsarendered3 v3.0b14 
>>
>
> I've merged the PR. pylint gives this complaint:
>
> * Module leo.plugins.viewrendered3
> leo\plugins\viewrendered3.py:1803:23: E0602: Undefined variable 
> 'AsciiDocError' (undefined-variable)
>
> Do you get the same complaint? If so, please attempt to remove it.  Thanks.
>

Actually, I knew about it.  I'm not sure if it's real or something that 
pylint doesn't understand (I think it's this).  I'll be looking at it.  If 
it's real, it will happen when the asciidoc3 processor raises that type of 
error, which I have seen but not very often. 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a44869a7-91ac-460d-8842-899a171cef1fo%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Edward K. Ream]

On Wednesday, September 2, 2020 at 10:30:08 PM UTC-5, Thomas Passin wrote:
>
> I've just submitted a pull request for viewsarendered3 v3.0b14 
>

I've merged the PR. pylint gives this complaint:

* Module leo.plugins.viewrendered3
leo\plugins\viewrendered3.py:1803:23: E0602: Undefined variable 
'AsciiDocError' (undefined-variable)

Do you get the same complaint? If so, please attempt to remove it.  Thanks.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/354be6ff-bea9-4198-97a6-f3c5e04cd430o%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

I've just submitted a pull request for viewsarendered3 v3.0b14 adding the 
ruby asciidoctor as an external rendering engine.  This has only been 
tested in Windows, so if anyone is interested, please try it out on Linux.  
See the help message for information on installing asciidoctor and on the 
setting needed to tell VR3 to use it.

On my system, asciidoctor prints an odd error message to the console:

Invalid switch - "Users".

This is nothing that VR3 sets up, so I speculate that it is something 
incorrect in an asciidoctor configuration file.  I'll try to track it down 
if no one knows about it.

On Wed, 2020-09-02 at 12:37 -0700, Thomas Passin wrote:
>
>
>
> On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin wrote:
>
> I've issued a PR for VR3, and otherwise it is available from my Git repo 
> on the vr3-asciidoc branch -
>
> https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
>
> I have found that Asciidoc processing is *much slower* than for RsT and 
> Md.  For example, 15k of Rst takes much less than a second to process but 
> 20k of Asciidoc text takes about 10 seconds on my computer, which is pretty 
> fast.  So I can't recommend rendering entire subtrees if they are long.  It 
> is likely that using the Ruby version of asciidoc would be much faster 
> (they claim a factor of 100), but I have not tested this.
>
>
> I just installed Ruby and the asciidoctor gem that it runs.  It did 
> convert that 20k asciidoc file in a twinkling.  I will get VR3 to use it 
> too, and see how that works out.
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "leo-editor" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/leo-editor/EJxEEFWSkRM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> leo-e...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/leo-editor/eba583db-6dfe-4d10-9084-9d6869b8fdd0o%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/7d27f2d4-79e0-40be-a9b4-e982ddb01157o%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[perceptiblelogic]

Nice!


On Wed, 2020-09-02 at 12:37 -0700, Thomas Passin wrote:
> 
> 
> On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin
> wrote:
> > I've issued a PR for VR3, and otherwise it is available from my Git
> > repo on the vr3-asciidoc branch -
> > 
> > https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
> > 
> > I have found that Asciidoc processing is much slower than for RsT
> > and Md.  For example, 15k of Rst takes much less than a second to
> > process but 20k of Asciidoc text takes about 10 seconds on my
> > computer, which is pretty fast.  So I can't recommend rendering
> > entire subtrees if they are long.  It is likely that using the Ruby
> > version of asciidoc would be much faster (they claim a factor of
> > 100), but I have not tested this.
> 
> I just installed Ruby and the asciidoctor gem that it runs.  It did
> convert that 20k asciidoc file in a twinkling.  I will get VR3 to use
> it too, and see how that works out.
> 
> 
> 
> 
> -- 
> 
> You received this message because you are subscribed to a topic in
> the Google Groups "leo-editor" group.
> 
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/leo-editor/EJxEEFWSkRM/unsubscribe.
> 
> To unsubscribe from this group and all its topics, send an email to 
> leo-editor+unsubscr...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/leo-editor/eba583db-6dfe-4d10-9084-9d6869b8fdd0o%40googlegroups.com
> .
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ead153d32c138ff056e1ccb91c6902df0e90cc56.camel%40gmail.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin wrote:
>
> I've issued a PR for VR3, and otherwise it is available from my Git repo 
> on the vr3-asciidoc branch -
>
> https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
>
> I have found that Asciidoc processing is *much slower* than for RsT and 
> Md.  For example, 15k of Rst takes much less than a second to process but 
> 20k of Asciidoc text takes about 10 seconds on my computer, which is pretty 
> fast.  So I can't recommend rendering entire subtrees if they are long.  It 
> is likely that using the Ruby version of asciidoc would be much faster 
> (they claim a factor of 100), but I have not tested this.
>

I just installed Ruby and the asciidoctor gem that it runs.  It did convert 
that 20k asciidoc file in a twinkling.  I will get VR3 to use it too, and 
see how that works out.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/eba583db-6dfe-4d10-9084-9d6869b8fdd0o%40googlegroups.com.

Re: New Version of Viewrendered3 Updates Asciidoc Handling.

[k-hen]

This is really excellent - and a very big help - thank you Tom :-)

Kevin

On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4 tbp1...@gmail.com wrote:

> I've issued a PR for VR3, and otherwise it is available from my Git repo 
> on the vr3-asciidoc branch -
>
> https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
>
> The processing for Asciidoc has been upgraded to be on a par with 
> reStructured Text and Markdown.  This means that it handles rendering an 
> entire subtree, code blocks only, Python code execution, and honors @/@c 
> and @image directives.  Trees and @language blocks need to use the name 
> "asciidoc" in language directives.  Note that this is *not* the same as 
> the adoc directive that Leo already has.
>
> There are some limitations, and not every Asciidoc construct hast been 
> tested:
>
> - an file include instruction inside a code block will not be understood.
> - Mathjax symbols and equations do not work even though the Asciidoc3 
> documentation suggests it should.
>
> I have found that Asciidoc processing is *much slower* than for RsT and 
> Md.  For example, 15k of Rst takes much less than a second to process but 
> 20k of Asciidoc text takes about 10 seconds on my computer, which is pretty 
> fast.  So I can't recommend rendering entire subtrees if they are long.  It 
> is likely that using the Ruby version of asciidoc would be much faster 
> (they claim a factor of 100), but I have not tested this.
>
> VR3 can use two Python versions of Asciidoc processors - the original 
> asciidoc 
> and the fork asciidoc3.  There is a setting to prefer one over the other, 
> e.g. -
>
> @bool vr3-prefer-asciidoc3 = False
>
> VR3 will try to import their code.  If that fails, it will fall back to 
> running the processor's executable file external to Leo, if that file can 
> be found.  On Windows, this means a file named asciidoc.exe or asciidoc.cmd 
> (or their asciidoc3 counterparts). The processor must be on the system path.
>
> There are some installation complications. asciidoc is available as a 
> zipped package and is not available via pip. Unzip it in some convenient 
> location.  VR3 has a new setting to tell it where the unzipped asciidoc 
> directory 
> is.  For example -
>
> @string vr3-asciidoc-path = D:\utility\asciidoc-9.0.2
>
> asciidoc3 is available via pip but needs a post-processing step to 
> complete its setup.  On some Windows installations this post-processing 
> step may fail.  If so, the asciidoc3 test program  will probably fail also, 
> as well as VR3's imported asciidoc3 code.  I have proposed fixes for these 
> bugs on the asciidoc3 github site.  You can make these fixes yourself if 
> you want.  See these threads for details -
>
> - https://github.com/asciidoc3/asciidoc3/issues/9
> - https://github.com/asciidoc3/asciidoc3/issues/10
>
> The maintainer seems to be interested in fixing the issues, so perhaps 
> soon there will be a new version available.  Pending this update, it might 
> be easier to use asciidoc instead.  I have not noticed performance 
> difference between the two processors.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c16335b5-56a4-43e3-af8c-eb896ee1be8an%40googlegroups.com.

New Version of Viewrendered3 Updates Asciidoc Handling.

[Thomas Passin]

I've issued a PR for VR3, and otherwise it is available from my Git repo on 
the vr3-asciidoc branch -

https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo

The processing for Asciidoc has been upgraded to be on a par with 
reStructured Text and Markdown.  This means that it handles rendering an 
entire subtree, code blocks only, Python code execution, and honors @/@c 
and @image directives.  Trees and @language blocks need to use the name 
"asciidoc" in language directives.  Not that this is *not* the same as the adoc 
directive that Leo already has.

There are some limitations, and not every Asciidoc construct hast been 
tested:

- an file include instruction inside a code block will not be understood.
- Mathjax symbols and equations do not work even though the Asciidoc3 
documentation suggests it should.

I have found that Asciidoc processing is *much slower* than for RsT and 
Md.  For example, 15k of Rst takes much less than a second to process but 
20k of Asciidoc text takes about 10 seconds on my computer, which is pretty 
fast.  So I can't recommend rendering entire subtrees if they are long.  It 
is likely that using the Ruby version of asciidoc would be much faster 
(they claim a factor of 100), but I have not tested this.

VR3 can use two Python versions of Asciidoc processors - the original asciidoc 
and the fork asciidoc3.  There is a setting to prefer one over the other, 
e.g. -

@bool vr3-prefer-asciidoc3 = False

VR3 will try to import their code.  If that fails, it will fall back to 
running the processor's executable file external to Leo, if that file can 
be found.  On Windows, this means a file named asciidoc.exe or asciidoc.cmd 
(or their asciidoc3 counterparts). The processor must be on the system path.

There are some installation complications. asciidoc is available as a 
zipped package and is not available via pip. Unzip it in some convenient 
location.  VR3 has a new setting to tell it where the unzipped asciidoc 
directory 
is.  For example -

@string vr3-asciidoc-path = D:\utility\asciidoc-9.0.2

asciidoc3 is available via pip but needs a post-processing step to complete 
its setup.  On some Windows installations this post-processing step may 
fail.  If so, the asciidoc3 test program  will probably fail also, as well 
as VR3's imported asciidoc3 code.  I have proposed fixes for these bugs on 
the asciidoc3 github site.  You can make these fixes yourself if you want.  
See these threads for details -

- https://github.com/asciidoc3/asciidoc3/issues/9
- https://github.com/asciidoc3/asciidoc3/issues/10

The maintainer seems to be interested in fixing the issues, so perhaps soon 
there will be a new version available.  Pending this update, it might be 
easier to use asciidoc instead.  I have not noticed performance difference 
between the two processors.


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/de05010a-4b92-42ac-a465-2f80b8754870o%40googlegroups.com.

Re: Viewrendered3 Updates

[Thomas Passin]

I really appreciate all these suggestions!  Unfortunately none of them have 
lead to success, although I've learned a few things.

Even after doing the unset credential.helper commands and creating a new 
remote, I get this:

C:\repos\leo-editor>git push leo_origin_2 devel
Username for 'https://github.com': tbpassin
Password for 'https://tbpas...@github.com':
remote: Permission to leo-editor/leo-editor.git denied to tbpassin.
fatal: unable to access 'https://github.com/leo-editor/leo-editor.git/': 
The requested URL returned error: 403

That's to say, the very same thing I've gotten all along.  I used my github 
user name and pw, the same ones I use to log into GitHub with.  I get the 
same whether I push from GitHub Extensions using the Push menu item, or by 
directly running git in a Windows cmd window.

Some things I've learned:

If you use the https://github ... URL, then no private key is involved, so 
it doesn't matter if you created one and told putty to use it.

You saw some github entries in the Windows Credentials Manager that you 
couldn't account for. I had them too. I discovered that after I had deleted 
them all, then the next time I tried to push to upstream that a new such 
entry had been created, with the user name being .  In the GitHub page that shows your personal tokens, I saw that a 
new one had been created.  There's no way to find out the actual value of 
that token, but git seems to know.

After I ran the unset credential.helper commands, I always got a 
username/pw dialog (as you did), and these credential entries didn't get 
added.

So that's all interesting but didn't get me connected.  I wonder if the Leo 
repo just doesn't have me marked as being able to push?

On Monday, April 20, 2020 at 4:20:31 PM UTC-4, Matt Wilkie wrote:
>
> Hmm, I wonder if that could be my Windows firewall preventing the outbound 
>> connection because it's ssh?
>>
>
> I get the same error, but I'm not using Putty/ssh to connect and don't 
> have any keys loaded.
>
> As I understand it (and I'm not sure I do understand it!) there 3 common 
> pathways on Windows for git authentication:
>
>- Putty and SSH keys
>- Windows Credentials (example below)
>- OAuth tokens (in Git Extensions see "Plugins>>Github" menu)
>
> I think it is possible to be have all 3 configured at once on a single 
> machine, but only using one at any given moment, through means opaque to me.
>
> On my main Leo computer going to "Control Panel\User Accounts\Credential 
> Manager >> Windows Credentials >> Generic" shows 2 github entries. I don't 
> know how these got setup initially, but I know on my work computer I was 
> able to add a github entry manually and that after that I could push. 
> Here's where I learned about Credential Manager: 
> https://github.com/gitextensions/gitextensions/issues/4916
>
>
>
> For my work computer troubles I took the step of resetting my credentials 
> and now enter my password every time. Painful but alway works.
>
> Clearing stored git username and passwords 
>
>  
>
> elevate git config --system --unset credential.helper
>
> git config --global --unset credential.helper
>
>  
>
> then for each repo:
>
>
> git config --unset credential.helper
>
>
> (*elevate *refers to https://code.kliu.org/misc/elevate/)
>
>
> And then go to "Control Panel\User Accounts\Credential Manager" >> Windows 
> Credentials >> Generic" and remove the GitHub entries. 
>
> After this using "git push" in console asked for credentials -- every time 
> though. Still need to figure out how to safely save them for re-use on this 
> machine.
>
> So, a bunch info, some of which may even be useful.
>
> Sign me, 
>
> *a-reluctant-git-user-who-resents-the-amount-time-required-for-stupid-git-administrivia*
> -matt
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/df950f33-86f4-4284-9597-a01ec66f2387%40googlegroups.com.

Re: Viewrendered3 Updates

[Matt Wilkie]

>
> Hmm, I wonder if that could be my Windows firewall preventing the outbound 
> connection because it's ssh?
>

I get the same error, but I'm not using Putty/ssh to connect and don't have 
any keys loaded.

As I understand it (and I'm not sure I do understand it!) there 3 common 
pathways on Windows for git authentication:

   - Putty and SSH keys
   - Windows Credentials (example below)
   - OAuth tokens (in Git Extensions see "Plugins>>Github" menu)
   
I think it is possible to be have all 3 configured at once on a single 
machine, but only using one at any given moment, through means opaque to me.

On my main Leo computer going to "Control Panel\User Accounts\Credential 
Manager >> Windows Credentials >> Generic" shows 2 github entries. I don't 
know how these got setup initially, but I know on my work computer I was 
able to add a github entry manually and that after that I could push. 
Here's where I learned about Credential Manager: 
https://github.com/gitextensions/gitextensions/issues/4916



For my work computer troubles I took the step of resetting my credentials 
and now enter my password every time. Painful but alway works.

Clearing stored git username and passwords 

 

elevate git config --system --unset credential.helper

git config --global --unset credential.helper

 

then for each repo:


git config --unset credential.helper


(*elevate *refers to https://code.kliu.org/misc/elevate/)


And then go to "Control Panel\User Accounts\Credential Manager" >> Windows 
Credentials >> Generic" and remove the GitHub entries. 

After this using "git push" in console asked for credentials -- every time 
though. Still need to figure out how to safely save them for re-use on this 
machine.

So, a bunch info, some of which may even be useful.

Sign me, 
*a-reluctant-git-user-who-resents-the-amount-time-required-for-stupid-git-administrivia*
-matt

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/2b4303d7-3d6a-4853-81b8-4f57f9bf448a%40googlegroups.com.

Re: Viewrendered3 Updates

[Edward K. Ream]

On Mon, Apr 20, 2020 at 9:52 AM Thomas Passin  wrote:

> I already had the upstream origin configured.  To follow your suggestions,
> I created a new one and deactivated the previous one.  I still get the same
> results, and in thedialog to manage remotes, using the  "Test Connection"
> button gave this:
>
> Unable to open connection:
> Host does not exist
>
> Hmm, I wonder if that could be my Windows firewall preventing the outbound
> connection because it's ssh?
>

I can't help you here. For now, could you please just email me your latest
vr3.py? I'll push it to devel myself.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1oQgECcC7UoRGNjj5KODgoO_EjnNB-CwW%3DFeptOjLZFQ%40mail.gmail.com.

Re: Viewrendered3 Updates

[Thomas Passin]

I already had the upstream origin configured.  To follow your suggestions, 
I created a new one and deactivated the previous one.  I still get the same 
results, and in thedialog to manage remotes, using the  "Test Connection" 
button gave this:

Unable to open connection:
Host does not exist

Hmm, I wonder if that could be my Windows firewall preventing the outbound 
connection because it's ssh?

On Monday, April 20, 2020 at 12:00:12 AM UTC-4, Matt Wilkie wrote:
>
>
> Hmm. What happens with `git push` from console?  (see tab button beside 
>>> [commit, diff, file tree, ...] in Git Extensions, or just from a regular 
>>> command prompt). Any error messages?
>>>
>>
>> That pushes to my fork, but not upstream to Leo.  It works fine.  Do you 
>> think it's worth cloning Leo using Git-Ext?  Right now, I have the fork, 
>> managed with Git Ext, and the Leo clone, managed by Github Desktop.
>>
>
> Ahh, I think I see now. You need to add a new remote to push to. This 
> could be done in any client, but I only know how for git extensions. Once 
> the remote(s) are set all the clients should be able to use them. Right now 
> in the GitExt manged repo the remote named "origin" is probably set to your 
> personal fork. 
>
> Right click on "Remotes"  >> select "Manage" >> then [+] to add a new 
> remote. Call it 'upstream' (or anything else that makes sense to you) and 
> put in Leo's repo address for url:
>
> https://github.com/leo-editor/leo-editor.git
>
> When you save changes the next prompt is confusingly worded. What it's 
> really asking is: *"make this new remote the default one?"*.
>
> From this point on, when you use the Push or Pull dialogs (via dropdown) 
> you can choose between Origin (yours) and Upstream (Leo Editor 
> organization) for the destination.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/135e2d50-a70d-44bc-ac4f-466ec67c9c8e%40googlegroups.com.

Re: Viewrendered3 Updates

[Matt Wilkie]

So that's (a very brief) intro for how to work with multiple remotes for a 
single source code repo. For me that's too complicated and I prefer this 
route:

   1. Clone Leo (using the client you like best)
   2. On your machine immediately checkout and Devel, and create a new 
   branch
   3. Make a teeny change, commit and push. (to verify your memberhsip in 
   Leo org works).
   4. copy your work into this new branch, commit, hack, push, repeat.

-matt

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/1baa6fb3-e0c8-4638-bb39-437528de385b%40googlegroups.com.

Re: Viewrendered3 Updates

[Matt Wilkie]

> Hmm. What happens with `git push` from console?  (see tab button beside 
>> [commit, diff, file tree, ...] in Git Extensions, or just from a regular 
>> command prompt). Any error messages?
>>
>
> That pushes to my fork, but not upstream to Leo.  It works fine.  Do you 
> think it's worth cloning Leo using Git-Ext?  Right now, I have the fork, 
> managed with Git Ext, and the Leo clone, managed by Github Desktop.
>

Ahh, I think I see now. You need to add a new remote to push to. This could 
be done in any client, but I only know how for git extensions. Once the 
remote(s) are set all the clients should be able to use them. Right now in 
the GitExt manged repo the remote named "origin" is probably set to your 
personal fork. 

Right click on "Remotes"  >> select "Manage" >> then [+] to add a new 
remote. Call it 'upstream' (or anything else that makes sense to you) and 
put in Leo's repo address for url:

https://github.com/leo-editor/leo-editor.git

When you save changes the next prompt is confusingly worded. What it's 
really asking is: *"make this new remote the default one?"*.

>From this point on, when you use the Push or Pull dialogs (via dropdown) 
you can choose between Origin (yours) and Upstream (Leo Editor 
organization) for the destination.


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b8cd5f2e-84af-47f3-9369-8766fbdf2881%40googlegroups.com.

Re: Viewrendered3 Updates

[Thomas Passin]

On Sunday, April 19, 2020 at 8:45:19 PM UTC-4, Matt Wilkie wrote:
>
> Hmm. What happens with `git push` from console?  (see tab button beside 
> [commit, diff, file tree, ...] in Git Extensions, or just from a regular 
> command prompt). Any error messages?
>

That pushes to my fork, but not upstream to Leo.  It works fine.  Do you 
think it's worth cloning Leo using Git-Ext?  Right now, I have the fork, 
managed with Git Ext, and the Leo clone, managed by Github Desktop.

Do you have more than one GitHub account? I've run into problems with Git 
> Extensions and multiple GitHub identities. I *think *I've sorted it now, 
> but I've thought that before.
>

Not so far as I know, and Git Ext only seems to know about the one. There 
is one thing in this area that's a little confusing to me.  I don't let 
GutHub show my real mailing address.  It has told me that in that case, It 
cooked up a different email address for me to use - but I don't understand 
for what purposes.  I've tried using that one too, and no joy.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ebb13e3c-a2a6-4486-96bf-0c0b68e421d5%40googlegroups.com.

Re: Viewrendered3 Updates

[Matt Wilkie]

Hmm. What happens with `git push` from console?  (see tab button beside 
[commit, diff, file tree, ...] in Git Extensions, or just from a regular 
command prompt). Any error messages?

Do you have more than one GitHub account? I've run into problems with Git 
Extensions and multiple GitHub identities. I *think *I've sorted it now, 
but I've thought that before.

-matt

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/52c61b1a-7f35-4b3c-a9e1-e1d678713b38%40googlegroups.com.

Re: Viewrendered3 Updates

[Thomas Passin]

Thanks, Matt!

On Saturday, April 18, 2020 at 8:13:59 PM UTC-4, Matt Wilkie wrote:
>
> That is very inspiring Thomas!
>

I'm still stuck on pushing my changes to the Leo repo.  Here's hoping you 
can help!  Edward told me he's added me to Leo's contributors, but every 
attempt I've made to push a file has failed with an Unauthorized or 403 
Forbidden error.   Here's what I've tried:

1. Push directly from a Git Leo clone, using GitHub Desktop;
2. Push from my own Leo fork, using Git Extensions (as you recommended);
3. In Git Extensions, set up Putty to create and use a key pair, and 
informed Github of the public key.

Within my own fork, I didn't have any trouble pushing or merging my 
changes.  But all of these failed when I tried to go to the Leo repo.  I'm 
out of ideas to try.

So far as I know, both GitHub desktop and Git Extensions use the command 
line behind the scenes.  Is there some other configuration thing at Github 
that needs to be done?

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/81495fe8-bfa4-4489-848d-766520beee5b%40googlegroups.com.

Re: Viewrendered3 Updates

[Matt Wilkie]

That is very inspiring Thomas!

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/58bd16ed-9325-483c-8a17-85e1fee9084f%40googlegroups.com.

Viewrendered3 Updates

[Thomas Passin]

I have updated the VR3 plugin with some bug fixes and minor changes, and 
more significantly by adding a new @image directive.  Edward (@ekr) had  
suggested this, and after some reflection I decided to try it out.  The new 
directive requires a url:

@image url-to-image

where the url can be absolute including a file: url to the file system, a 
relative url (relative to the directory your outline is in), or a data: 
url. 
The new directive works for both Markdown and Restructured Text trees.

For the time being, the updated version is available from my fork on 
Github.  It is in the devel branch of

https://github.com/tbpassin/leo-editor

I'll push it to the upstream Leo distro once I work out how to persuade 
Github that yes, I'm supposed to be authorized to do that.

Please let me know of any bugs you find!


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ecf3ac4d-e53b-4368-afbe-34247fbb2933%40googlegroups.com.