On Monday, February 16, 2015 at 5:46:12 AM UTC-6, Edward K. Ream wrote:
>
> On Sunday, February 15, 2015 at 12:11:00 PM UTC-6, vitalije wrote:
>>
>>
>> Whenever I open leo file with @nosent nodes, Leo reports Recovered nodes.
>> All those nodes are using multiline comments between @ and @c direc
On Sunday, February 15, 2015 at 12:11:00 PM UTC-6, vitalije wrote:
>
>
> Whenever I open leo file with @nosent nodes, Leo reports Recovered nodes.
> All those nodes are using multiline comments between @ and @c directives.
> With every opening Leo adds single line comments in front of those lines
On Sun, Feb 15, 2015 at 1:14 PM, Edward K. Ream wrote:
> ...
> a post-pass after the update algorithm is the only good solution.
>
As I have just written in another thread, Leo's @file read code probably
already does such a post pass. There is an Easter Egg convention that
determines where
On Sunday, February 15, 2015 at 1:07:02 PM UTC-6, vitalije wrote:
>
>
> As I said, I could live with such restriction, but it would help if Leo
> change such blocks of code without user intervention. I think that no user
> using @nosent would object this Leo behaviour.
>
I agree completely. It
> I am wondering whether it might not be better simply to prohibit @...@c in
> @nosent files. How odious would that be for you?
>
> Edward
>
As I said, I could live with such restriction, but it would help if Leo
change such blocks of code without user intervention. I think that no user
using
On Sun, Feb 15, 2015 at 12:47 PM, vitalije wrote:
>
> Well, I could live without @ and @c, but it would be useful if Leo delete
> @ and @c lines and replace all those lines with properly language specific
> commented block.
>
You answered my question before I asked it.
Alas, prohibiting @...@c
On Sunday, February 15, 2015 at 12:11:00 PM UTC-6, vitalije wrote:
>
>
> I have updated my Leo installation yesterday and bumped in a bug with new
> @nosent code. Most of my files have been kept in @nosent nodes. Whenever I
> open leo file with @nosent nodes, Leo reports Recovered nodes. All thos
>
> This is a nasty problem. It's been around since day one of the @shadow
> algorithm, but it's only been reported now. It will requires some kind of
> special case for @...@c. I'll have to think about what is the best way to
> proceed.
>
> Edward
>
Well, I could live without @ and @c, bu
On Sun, Feb 15, 2015 at 12:11 PM, vitalije wrote:
> Hello,
> I have updated my Leo installation yesterday and bumped in a bug with new
> @nosent code. Most of my files have been kept in @nosent nodes. Whenever I
> open leo file with @nosent nodes, Leo reports Recovered nodes. All those
> nodes ar
On Sun, Feb 15, 2015 at 12:11 PM, vitalije wrote:
> Hello,
> I have updated my Leo installation yesterday and bumped in a bug with new
> @nosent code. Most of my files have been kept in @nosent nodes. Whenever I
> open leo file with @nosent nodes, Leo reports Recovered nodes. All those
> nodes ar
about my installation: Ubuntu 14.04
** isPython3: False
Leo 5.0-final, build 20150127110559, Tue, Jan 27, 2015 11:05:59 AM
Git repo info: branch = master, commit = f2ca65ecf8e8
Python 2.7.6, PyQt version 4.8.6
linux2
Vitalije
--
You received this message because you are subscribed to the Google
Hello,
I have updated my Leo installation yesterday and bumped in a bug with new
@nosent code. Most of my files have been kept in @nosent nodes. Whenever I
open leo file with @nosent nodes, Leo reports Recovered nodes. All those
nodes are using multiline comments between @ and @c directives. Wit
12 matches
Mail list logo
