Leo documentation

[rengel]

Have you ever thought of publishing Leo's documentation on ReadTheDocs 
(https://readthedocs.org/)? This might help 'mainstreaming' Leo.

-- 
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/a7837188-8a48-478c-a4fb-d241239d8f81%40googlegroups.com.

Rev 8d7006 in devel uses triple double quotes for all docstrings

[Edward K. Ream]

This has been a minor irritation for some time.

I have reviewed all the substitutions. The new code passes all tests.

I have retained triple *single* quotes where they are not used as 
docstrings.

I have no plans to change single quotes, of either kind.

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/92b32432-6a87-43ab-94ae-ceafbbde4a02%40googlegroups.com.

Re: Pytest command

[Brian Theado]

Vitalije,

I was looking at the execute-pytest code and it looked to me like only the
assertion rewrite functionality from pytest is being used. I would guess
none of the hooks or fixtures and maybe most plugins will work.

I don't much trust my code reading so I figured I'd better test it, but I
only got a stack trace when trying with your example:

Traceback (most recent call last):

  File "/home/btheado/src/leo-editor/leo/core/leoGlobals.py", line
293, in new_cmd_wrapper
func(self, event=event)

  File "/home/btheado/src/leo-editor/leo/core/leoCommands.py", line
729, in execute_pytest
self.execute_single_pytest(p)

  File "/home/btheado/src/leo-editor/leo/core/leoCommands.py", line
761, in execute_single_pytest
rewrite_asserts(tree, script, config=cfg)

  File 
"/home/btheado/src/pyqt-3.7-venv/lib/python3.7/site-packages/_pytest/assertion/rewrite.py",
line 327, in rewrite_asserts
AssertionRewriter(module_path, config, source).run(mod)

  File 
"/home/btheado/src/pyqt-3.7-venv/lib/python3.7/site-packages/_pytest/assertion/rewrite.py",
line 572, in __init__
"enable_assertion_pass_hook"

  File 
"/home/btheado/src/pyqt-3.7-venv/lib/python3.7/site-packages/_pytest/config/__init__.py",
line 976, in getini
self._inicache[name] = val = self._getini(name)

  File 
"/home/btheado/src/pyqt-3.7-venv/lib/python3.7/site-packages/_pytest/config/__init__.py",
line 987, in _getini
value = self.inicfg[name]

AttributeError: 'Config' object has no attribute 'inicfg'

python 3.7.3 and pytest 5.2.0

Do you have any ideas?

On Thu, Sep 26, 2019 at 6:31 AM vitalije  wrote:

> Hm, looking in the output it seems that the name of the test node, and
> failed test function in the output are missed. Revision 064e218
>  fixes this. Now the
> output is like:
>
> ---example/test_a failed-
> assert 4 == 4.1
>  +  where 4 = inc(3)
> ---example/test_b failed-
> assert 18.297 == 18
>  +  where 18.297 = times_3(6.1)
>  +where 6.1 = add_2(4.1)
>  +  where 4.1 = inc(3.1)
>  +  and   18 = times_3(6)
>  +where 6 = inc(5)
> failed:2 tests
>
> Vitalije
>
> --
> 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/b7880eb4-9c2f-4d37-932d-d1f0d72fcfe3%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/CAO5X8Cwq6XSp%2B3gRnTiWzcSyVMSYxbYgeWV43togHiB_7x4eGA%40mail.gmail.com.

Re: Looking for documentation about automatic setting of dirty flag

[Edward K. Ream]

On Wed, Oct 2, 2019 at 3:47 PM Robert Cholette 
wrote:

> I open leoPyRef.leo and unfold the code node, and then the core classes
node. Then just type a single letter in the body pane of 'core classes' :
all @files below are now dirty... is this normal?

Yeah, it's normal.  Probably because directives in ancestor nodes affect
child nodes.  So what I said previously isn't accurate.

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/CAMF8tS0VsH3Uf93mPG9_ygNPPYDC91r3nMrfoVTG%3DWsn-emFLA%40mail.gmail.com.

Re: Looking for documentation about automatic setting of dirty flag

[Robert Cholette]

> Setting a node dirty will not set any children dirty.

Can you elaborate? When I write text in the body of a node that has direct 
children that are @clean or @files, those children become dirty.

For example, I open leoPyRef.leo and unfold the code node, and then the 
core classes node. Then just type a single letter in the body pane of 'core 
classes' : all @files below are now dirty... is this normal? 
here's my log pane :
Leo 6.0-final, master branch, build f3e2b18bcd
2019-08-10 20:34:57 -0400
Python 3.6.8, PyQt version 5.9.5
linux
read 175 files in 0.37 seconds
read outline in 0.45 seconds

On Tuesday, October 1, 2019 at 4:37:38 PM UTC-4, Robert Cholette wrote:
>
> Just lookig for docum or part of code that would explain it.
>
> Particularly about when the parent is set dirty too (editing a body of 
> child of derived file-node)
> or when the childs are also set dirty... upon modifying body text of 
> parent if already had content/ or not.
>
> etc...
> Thanks! 
>
>

-- 
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/971c92cc-418e-4190-86af-1b3ae1ac7f55%40googlegroups.com.

Re: Discuss: is it time to retire the python_terminal plugin?

[Edward K. Ream]

On Tuesday, October 1, 2019 at 8:32:09 AM UTC-5, Edward K. Ream wrote:

> #1155  suggests 
retiring the python_terminal plugin.

Upon further review, I am not going to do this, for the following reasons:

1. #1212  apparently 
fixed the segfault problem, at the cost of disallowing tab completion.
2. User's shouldn't have to enable the pyzo_in_leo plugin to get the same 
features.
3. Rev c000b2f in devel adds some warnings, visible in the `@file 
python_terminal.py` node.

In short, this issue is make work.

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/5d844f80-ba97-46cc-a7cb-821357319d28%40googlegroups.com.

Re: For devs: the new "delegated" label

[Edward K. Ream]

On Wed, Oct 2, 2019 at 1:40 AM vitalije  wrote:

I'm impressed with your fix. It seems so easy, now that I saw it.
>

Thanks.

> I do apologize for all the fuss I have made about it, I was wrong.
>

No apology needed. I wouldn't have taken the issue seriously without you.

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/CAMF8tS3FS8Bb4AAFD5%2BQ5tM5h3VTx1%2B_P-W%2BFtD5fzOpRtaxpw%40mail.gmail.com.

Re: Looking for documentation about automatic setting of dirty flag

[Edward K. Ream]

On Tue, Oct 1, 2019 at 3:38 PM Robert Cholette 
wrote:

> Just looking for docs or part of code that would explain it.
>

Because of clones, the code is complex. Don't bother trying to understand
the code's intent from reading it :-)

We want to mark a node "dirty" (changed) if its headline or body text has
changed since the last time we last saved the outline (.leo file).  More
importantly, we want to mark the node that creates the external file dirty
as well, so Leo (and you) can know which files need to be written when we
save the .leo file.

Setting a node dirty will not set any children dirty.

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/CAMF8tS2xyce1zBw%3D2bi6_5ORrvjioBRMGQGZ7xeRbDqakoOKYQ%40mail.gmail.com.

Re: For devs: the new "delegated" label

[vitalije]

On Monday, September 30, 2019 at 6:56:00 PM UTC+2, Edward K. Ream wrote:
>
>
> I'll look into this. We are past the point were additional explanations 
> would be useful.
>
> Edward
>

I'm impressed with your fix. It seems so easy, now that I saw it. 
I do apologize for all the fuss I have made about it, I was wrong.
Vitalije
 

-- 
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/9b09ebe7-968e-4ce6-892c-f71caae720c5%40googlegroups.com.