I just noticed an @persistence node in my .leo file that contains numerous
@auto-rst nodes.
1. I never noticed them before, so I don't know if this is something new
(using the latest Git pull).
2. This node contains child nodes of the form: @data:@auto-rst
[filename.txt] and these
> Please send me the .leo file and external file so I can track down what
is happening.
Sent.
On Sun, Feb 15, 2015 at 1:29 PM, Edward K. Ream wrote:
> On Sun, Feb 15, 2015 at 11:55 AM, Steve Zatz wrote:
>
>> > Thanks for this. The fix is at rev 16981fd. All tests pass.
>>
>> Unfortunately, not
We have problem with @ and @c directives. For most languages I can think of
it would suffice if Leo just replace those blocks, along with directives,
with properly block commented text. But for @rst files those blocks are
used for special @rst-options.
What if Leo before writing Leo-outline r
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
On Sunday, February 15, 2015 at 12:41:44 PM UTC-6, vitalije wrote:
>
> For quite a long time I have noticed that command goto global line (Alt+G)
> doesn't work properly on @nosent files. It seems that it counts
> non-existing sentinel lines so it positions cursor few lines before the
> requeste
>
> 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
For quite a long time I have noticed that command goto global line (Alt+G)
doesn't work properly on @nosent files. It seems that it counts
non-existing sentinel lines so it positions cursor few lines before the
requested. The exact difference between required line number and found one
depends o
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 11:55 AM, Steve Zatz wrote:
> > Thanks for this. The fix is at rev 16981fd. All tests pass.
>
> Unfortunately, not fixed but a different log message.
>
Thanks for this. Please send me the .leo file and external file so I can
track down what is happening.
Edward
--
Y
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
> Thanks for this. The fix is at rev 16981fd. All tests pass.
Unfortunately, not fixed but a different log message. I no longer get the
listing of the old and new sentinels but I still get the message that the
input file is corrupted and I don't get any of the classes after the first
(which does
On Sun, Feb 15, 2015 at 6:15 AM, Steve Zatz wrote:
> I have a python file with a couple of lines that look like:
>
>
> #@xxx
> ...
>
Thanks for this. The fix is at rev 16981fd. All tests pass.
I was not able to get a new @shadow tests to fail with the old code, but a
hand
On Sat, Feb 14, 2015 at 12:50 PM, gatesphere wrote:
>
@auto-md is useful for the same reasons. And afaik, is completely
undocumented.
Thanks for this heads up. I'll make sure all flavors of @auto-* are
documented for 5.1. For sure, @auto will remain for the foreseeable
future.
Thi
I have a python file with a couple of lines that look like:
#@
I am not 100% sure this is the problem but if you look at the log file
below (edited to shorten it), the only difference between the first and
second set of sentinels is the indentat
On Sat, Feb 14, 2015 at 9:05 PM, wrote:
> all these commands that you have recently changed need proper
> documentation, once the dust has settled.
>
Thanks for this reminder. I've just put it on the list.
>
> There were also some obscure points I came across while reading the manual
> som
20 matches
Mail list logo
