On Sun, Jun 22, 2014 at 2:26 PM, David McNab wrote:
> However, with numerous Python files, @shadow has been inaccurately writing
> out files.
David, did Terry's suggestion help?
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubs
On Mon, 23 Jun 2014 07:26:58 +1200
David McNab wrote:
> However, with numerous Python files, @shadow has been inaccurately
> writing out files. The main inaccuracies have been to do with indent
> levels for significant blocks of code (a massive dealbreaker in
> Python), which unless resolved make
On Sun, Jun 22, 2014 at 2:26 PM, David McNab wrote:
> Hi all,
Hi David. Great to hear from you again.
Could you provide a smallish example of an @shadow file that Leo
doesn't write correctly? I'll give fixing such a bug high priority.
Edward
--
You received this message because you are subs
On Mon, 23 Jun 2014 07:26:58 +1200
David McNab wrote:
[snip]
> However, with numerous Python files, @shadow has been inaccurately
> writing out files. The main inaccuracies have been to do with indent
> levels for significant blocks of code (a massive dealbreaker in
> Python), which unless resolv
Hi all,
I've been a grateful Leo user for over 10 years now, and it's been a major
foundation tool in many of my software projects.
I'm now working in a team for the first time in years, and we're having to
share code via Git. I was expecting that @shadow nodes would solve the
problem - allow me
