install directories also, then pip will
find them and be able to properly list pyqt6 as well as the pyqt5 that is
in the standard location.
On Monday, April 12, 2021 at 5:24:50 PM UTC-4 tbp1...@gmail.com wrote:
> Typo:
> NoFrame = QtWidgets.QFrame.Shape.NoFrame if isQt6 else self.noFrame
>
Typo:
NoFrame = QtWidgets.QFrame.Shape.NoFrame if isQt6 else self.noFrame
should be
NoFrame = QtWidgets.QFrame.Shape.NoFrame if isQt6 else self.NoFrame
With this correction, it runs when only qt5 is available.
On Monday, April 12, 2021 at 2:59:44 PM UTC-4 tbp1...@gmail.com wrote:
> I
AS best as I can tell, QtWebEngine isn't available yet for qt6. The github
site for it only refers to qt5.15 as the latest reference I see. I maybe
had better remove qt6 from my everyday Python installation.
On Monday, April 12, 2021 at 2:59:44 PM UTC-4 tbp1...@gmail.com wrote:
> Next
The shift and ALT keys also do the same thing - delete the selection. The
strange characters get inserted when I press . This is using qt6,
of course.
On Monday, April 12, 2021 at 3:58:32 PM UTC-4 tbp1...@gmail.com wrote:
> Major problem - in the body pane, when I highlight a line of t
:35 PM UTC-4 tbp1...@gmail.com wrote:
> On Monday, April 12, 2021 at 2:59:44 PM UTC-4 tbp1...@gmail.com wrote:
>
>> I got qt_text to work - at least on the surface - with these changes:
>>
>#width = self.fm.width(str(max(1000,
>> self.high
On Monday, April 12, 2021 at 2:59:44 PM UTC-4 tbp1...@gmail.com wrote:
> I got qt_text to work - at least on the surface - with these changes:
>#width = self.fm.width(str(max(1000,
> self.highest_line))) + self.w_adjust
> if isQt6:
>
That's what I did with qt_text, except for using EditPlus instead.
On Monday, April 12, 2021 at 3:30:18 PM UTC-4 Edward K. Ream wrote:
> On Mon, Apr 12, 2021 at 12:26 PM tbp1...@gmail.com
> wrote:
>
>> As a practical matter, how are you managing to edit one of these files
&g
know if
you want the PR.
Next up: VR3 won't load because
viewrendered3.py requires QtWebKitWidgets.QWebView
pip install PyQtWebEngine
But how to get this without stepping on the one for qt5? Hmmm.
On Monday, April 12, 2021 at 1:57:39 PM UTC-4 tbp1...@gmail.com wrote:
> It failed beca
It failed because
LeoLineTextWidget' object has no attribute 'StyledPanel
as expected ...
On Monday, April 12, 2021 at 1:03:57 PM UTC-4 Edward K. Ream wrote:
> On Monday, April 12, 2021 at 11:55:03 AM UTC-5 tbp1...@gmail.com wrote:
>
> Without testing it I don't think that
With Sphinx/Rst you can change the css stylesheet and get it to use yours
instead. For example, the difference between the appearance of the docs on
the Sphinx site and those on ReadTheDocs is the CSS stylesheet. I'm not
sure how you can get Sphinx to use a newly named style - one that it
command to copy it to my repo working directory. That works pretty well
for one file, but it would be cumbersome for a lot of them.
On Monday, April 12, 2021 at 1:03:57 PM UTC-4 Edward K. Ream wrote:
> On Monday, April 12, 2021 at 11:55:03 AM UTC-5 tbp1...@gmail.com wrote:
>
> Without tes
self.setFrameStyle(Raised | Sunken)
Also, couldn't *self.Shadow* be used instead of *QtWidgets.QFrame.Shadow*?
On Monday, April 12, 2021 at 11:59:16 AM UTC-4 Edward K. Ream wrote:
> On Mon, Apr 12, 2021 at 10:32 AM tbp1...@gmail.com
> wrote:
>
>> Looks like the names of the constants ha
:10 AM UTC-4 Edward K. Ream wrote:
> On Mon, Apr 12, 2021 at 10:13 AM tbp1...@gmail.com
> wrote:
>
>> I got a large number of messages as Leo tried to start. Here is the last
>> one before it quit:
>>
>> File "d:\Tom\git\leo-editor\
I got a large number of messages as Leo tried to start. Here is the last
one before it quit:
File "d:\Tom\git\leo-editor\leo\plugins\qt_text.py", line 413, in __init__
self.setFrameStyle(self.StyledPanel | self.Sunken)
AttributeError: 'LeoLineTextWidget' object has no attribute
allowed languages, and there is a new sql.py file in
modes to do the sql colorization.
Of course, this version doesn't work in the devel branch yet, only the
ekr-qt one.
On Sunday, April 11, 2021 at 7:54:42 PM UTC-4 Edward K. Ream wrote:
> On Sun, Apr 11, 2021 at 9:29 AM tbp1...@gmail.
exist until wanted later.
On Sunday, April 11, 2021 at 7:54:42 PM UTC-4 Edward K. Ream wrote:
> On Sun, Apr 11, 2021 at 9:29 AM tbp1...@gmail.com
> wrote:
>
>>
>>
>> On Sunday, April 11, 2021 at 5:31:59 AM UTC-4 Edward K. Ream wrote:
>>
>>>
>>> 4
The VR3 plugin for Leo can render Asciidoc to HTML using an Ascidoc command
line processor, and then display it inside Leo in its display pane. I have
found that the conversion is slow for larger asciidoc trees, though (not
because of Leo but because of the processor). The flavor of HTML
New issue # 1889 at
https://github.com/leo-editor/leo-editor/issues/1889
On Sunday, April 11, 2021 at 3:42:02 AM UTC-4 Edward K. Ream wrote:
> On Sat, Apr 10, 2021 at 10:46 PM tbp1...@gmail.com
> wrote:
>
>> Unfortunately, there is a fly in the ointment.
>>
>
I instrumented *expand_path_expression**()* with print statements and found
that it is being called all the time, apparently for every file that Leo
knows about. I'm thinking that it's Leo polling to see if each file has
been changed outside of Leo. Some of those call outputs were full paths,
On Sunday, April 11, 2021 at 5:31:59 AM UTC-4 Edward K. Ream wrote:
>
> 4. I have just fixed some problems in the VR3 plugin. It now loads
> properly, but I make no claim that it works in all respect. I don't
> remember who wrote VR3, but we'll have to work out a way to support qt6.
>
That's
if there is a file here.
#if fn:
#steps.append(fn)
if len(steps) > 1:
pth = os.path.join(steps[0], *steps[1:])
elif len(steps) == 1:
pth = steps[0]
else:
pth = os.getcwd()
pth = os.path.expanduser(pth)
if g.isWindows:
pth = pth.replace('/', '\\')
else:
On Saturday, April 10, 2021 at 10:12:42 AM UTC-4 TEK42 wrote:
> Good find. That change works well for OS X too. Additionally, environment
> variables can be handled:
> ...
> I've installed from the devel git branch, so I'll just go ahead and look
> into how to contribute to this project. I'd
This fix works on Windows, too - the "~" expands correctly to my user home
directory.
On Friday, April 9, 2021 at 10:11:49 PM UTC-4 tbp1...@gmail.com wrote:
> It looks like there is a simple fix. This hasn't had hardly any testing,
> but on the surface it's doing the right th
It looks like there is a simple fix. This hasn't had hardly any testing,
but on the surface it's doing the right thing. The little example that
failed in an earlier post created the right directories.
In *leoCommands.py*, in the method *expand_path_expression(self, s)*, add
the line marked
his would
be to adjust, because you would only want to substitute */home/{user}* for
"~" if it appears at the start of a path expression, and I don't know yet
how to know. Also, it needs to be checked if a change here would cause
troubles anywhere else.
On Friday, April 9, 2021 at 1:
I recreated that example file tree on Linux, and darned if I didn't get
the same result as you. I must have had my eyes see the "~" and start
reading from there because that's what I expected to see. So, a real bug
and not just a Mac quirk.
In fact, I get the same behavior on Windows. It's
I don't have a Mac, so I can't help much, but I can speak a bit about the
*@path
~* matter. This does work on Linux. When you wrote "does not expand", did
you mean that the implied paths are not created when you save an "external"
file? If so, you can change this behavior by adding a node
ou want to get the file path if the node is an external file node, or
the directory path if it's not, this will do the job:
os.path.abspath(g.fullPath(c, p))
On Wednesday, April 7, 2021 at 10:58:24 AM UTC-4 Edward K. Ream wrote:
> On Tuesday, April 6, 2021 at 9:51:34 PM UTC-5 tbp1.
s). I now realize that I have made use of that
behavior without realizing that it might have been different.
On Tuesday, April 6, 2021 at 10:40:58 PM UTC-4 tbp1...@gmail.com wrote:
> OK, after some more testing and thought:
>
> 1. Edward's example can't work as claimed, even if '.' is r
find its parent directory.
On Tuesday, April 6, 2021 at 5:58:43 PM UTC-4 tbp1...@gmail.com wrote:
> But in your snippet, you also use "." without (apparently) changing it.
>
> import os
> from subprocess import run
> path = g.fullPath(c, p) or os.path.abspath('.')
>
&
On Tuesday, April 6, 2021 at 5:18:14 PM UTC-4 tbp1...@gmail.com wrote:
> But I suppose it would be better to use a more comprehensive method in
> case you accidentally delete this "feature" in the future.
>
> On Tuesday, April 6, 2021 at 5:16:54 PM UTC-4 tbp1...@gmail.com wro
But I suppose it would be better to use a more comprehensive method in case
you accidentally delete this "feature" in the future.
On Tuesday, April 6, 2021 at 5:16:54 PM UTC-4 tbp1...@gmail.com wrote:
> Well, it's more than that. Using "." works for @path subtre
, 2021 at 10:29 AM tbp1...@gmail.com
> wrote:
>
>>
>>
>> On Tuesday, April 6, 2021 at 10:14:19 AM UTC-4 Edward K. Ream wrote:
>>
>>> On Tue, Apr 6, 2021 at 7:15 AM tbp1...@gmail.com
>>> wrote:
>>>
>>> BTW, I have put a button in
a
> window-manager-agnostic way under (most?) linuxes. I'll give it a try...
>
> On Tuesday, April 6, 2021 at 1:15:52 PM UTC+1 tbp1...@gmail.com wrote:
>
>> Here's what I have been doing to create files in directory trees. It
>> seems much simpler.
>>
>> 1. Create a
On Tuesday, April 6, 2021 at 10:14:19 AM UTC-4 Edward K. Ream wrote:
> On Tue, Apr 6, 2021 at 7:15 AM tbp1...@gmail.com
> wrote:
>
> BTW, I have put a button into MyLeoSettings.leo that will open a file
>> manager window (File Explorer on Windows) at the current directory o
Here's what I have been doing to create files in directory trees. It seems
much simpler.
1. Create a node with the headline *@path d:\temp\aaa*
2. Create a path with the headline *@path bbb*. Indent it right, under the
*aaa* one.
3. ... and so on
4. However far down in the tree you like,
Not on my Win 10 OS, though. Windows+Spacebar doesn't bring up anything.
There is a Settings page for keyboard and regional settings (Edit Language
and Keyboard Settings). It has many different varieties of English (e.g.,
English (Botswana)), but I didn't find a "International" option.
the source control issue of controlling both the outline and
the derived files that I'm mulling over. Of course, the easiest way is to
source-control both, and maybe I'll start doing that.
On Sunday, April 4, 2021 at 8:13:29 AM UTC-4 Edward K. Ream wrote:
> On Sat, Apr 3, 2021 at 5:06 PM t
I've had a few cases where the external file for an *@clean* tree went
missing. This causes the file to be empty with no recovery unless there is
a backup. This makes me want to turn all of them into *@file* trees. But
there are times I want to emit a clean file - no sentinels, etc.
Most
My primary document built with Sphinx without trouble as far as I can see.
It has a tree with 15 @rst nodes, some of which are *contain a @rst-no-head*
node. The built html files come to something over 500KB, so not huge but
not a toy document, either. This tree does not call for any of the
On Sunday, March 28, 2021 at 2:25:22 PM UTC-4 Edward K. Ream wrote:
> Presumably you are using @bool rst3_call_docutils = False, as in
> LeoDocs.leo. That option creates intermediate (.html.txt) files for use by
> sphinx, without calling docutils.
Actually, I have it set to True. I'll try
will be happy. If it won't, I will probably have to do a
lot of work to be able to generate my documentation, and I won't like that.
On Saturday, March 27, 2021 at 5:37:39 PM UTC-4 Edward K. Ream wrote:
> On Saturday, March 27, 2021 at 11:52:00 AM UTC-5 tbp1...@gmail.com wrote:
>
> Every
I'm not saying anything against what you say, not at all. I'm just
suggesting that the end result might better be named by a different name,
presumably "rst4".
On Saturday, March 27, 2021 at 7:12:28 PM UTC-4 Edward K. Ream wrote:
> On Saturday, March 27, 2021 at 4:37:39 PM UTC-5 Edward K.
However, the title of Viktor's post implies a valid suggestion. Everything
you say you want to achieve could be done by leaving rst3 as is - never
touching it again - and creating a new rst4. It would be no more work, and
there would be no latent backwards compatibility issues.
In fact, it
I use rst3 to generate Sphinx documentation and I have been happy with it.
I was not aware of all these configuration options and have not missed them.
Instead of changing the rst3 code, we could consider just not telling
people about these options, or advising them not to use any. Would not
I suggest a name change for *save-as-xml*. "xml" is too generic. I presume
you mean to save as a standard leo outline. Maybe *save-as-leo-outline*,
or *save-as-dotleo*. Otherwise someone might suppose that the saved file
will be some new xml format that isn't openable by Leo.
On Tuesday,
Please don't rush into this. 3.9 is not yet offered on some (many?) Linux
distros, including Debian and Mint (I don't know about non-Debian-based
ones). And even on Windows, it's often hard to impossible to find 64-bit
packages that require compiled binary modules for recent versions of
her the
> 'numlock' key is on or off. When off:
>
> 1: End
> 2: down
> 3: Pg. Ddown
> 4: left
> 5: N/A
> 6: right
> 7: home
> 8: up
> 9: Page up
>
> These are marked, on my keyboards at least.
>
>
> On Sunday, March 21, 2021 at 3:17:55 PM UTC tbp1...@gmail.com wrot
My keypad does not have a "Home" key, and I can't remember any that did. I
see there are other similar shortcuts, like Alt+Keypad+End, for
non-existent keys. What keyboard actions are intended here?
On Sunday, March 21, 2021 at 8:23:44 AM UTC-4 Edward K. Ream wrote:
> On Sat, Mar 20, 2021 at
Once you have some version of Leo working - say, 6.1 - you can run other
versions without actually installing them.
A simple way to run any particular Leo version from GitHub is to get the
zip file for that branch presumably *devel *- make sure you switch to the
*devel* branch before getting
@gmail.com wrote:
> tbp1...@gmail.com schrieb am Freitag, 12. März 2021 um 22:38:31 UTC+1:
>
>> I tried downgrading Leo to 6.0, but it still failed with the same error.
>> Then I downgraded PyQt5 to 5.15.1. I then downgraded PyQtWebEngine - but
>> spelled all lo
, but there is an error somewhere in the pip
instruction files.
On Friday, March 12, 2021 at 4:22:38 PM UTC-5 viktor@gmail.com wrote:
> Viktor Ransmayr schrieb am Freitag, 12. März 2021 um 22:09:20 UTC+1:
>
>> Am Fr., 12. März 2021 um 19:19 Uhr schrieb tbp1...@gmail.com <
>&
r.
Online, it seems that others have had this problem with non-python Qt5
installations. Several people have found fixes that worked for them but
not for others. So far, I don't have a solution but apparently there is
one to be found.
On Friday, March 12, 2021 at 1:19:27 PM UTC-5 tbp1...@gmail.
I just installed a Debian VM. After installing Leo with pip I got exactly
the same error message as you. I don't know what to do with it, though.
On Friday, March 12, 2021 at 12:29:34 PM UTC-5 viktor@gmail.com wrote:
> tbp1...@gmail.com schrieb am Freitag, 12. März 2021 um 15:44:31 UT
I can't help directly with Debian, but Leo works fine on my VMs running
both Mint and Ubuntu, which are both Debian-based. I would have thought
that they use Debian packages directly, but maybe that's not so.
On Mint, I have only three Qt packages installed:
$python3 -m pip list |grep "Qt"
Here is a little trick to catch functions or methods that you haven't
implemented yet. It's useful when you sketch out the structure of a
program but the functions/methods don't do anything yet. Typically you
write the signature of the function but the only line of code is pass.
The last
I have found that getting too many levels in a mind map ends up being
cluttered and confusing. One central image and some branches that get two
deep are enough for me. For outlining, at some point you will become
interested in the order. I have found that ordering the branches around
the
I really like mind maps, too. And mostly I don't like existing mind map
software. For a book I wrote, I made a simple mind map for some of the
chapters. Then I started to flesh them out, which a mind map really
stimulates the thinking. It worked very well.
I also find that a basic mind map
Thanks, Edward.
On Saturday, March 6, 2021 at 6:54:44 AM UTC-5 Edward K. Ream wrote:
> On Fri, Mar 5, 2021 at 10:27 PM tbp1...@gmail.com
> wrote:
>
> Is there a way to have an @clean or @file tree that is valid Python 2, and
>> save it despite Python 3 errors?
>>
>
I have some @clean trees in one or another Leo outline (and probably some
@file ones also), ones that I haven't happened to open for several years.
Of course, Leo now runs under Python 3. So when I go to save these files,
Leo thinks there is a syntax error and won't save them.
I don't know
ike the help message to not mislead me :).
On Friday, March 5, 2021 at 9:09:35 AM UTC-5 Edward K. Ream wrote:
> On Fri, Mar 5, 2021 at 8:06 AM tbp1...@gmail.com
> wrote:
>
> I didn't get any output from the mypy command. This code is in a node,
>> and it's not an @file or @anythi
I didn't get any output from the mypy command. This code is in a node, and
it's not an @file or @anything node:
@language python
def f1(x:int) -> int:
y:int = 3*x
return 'this is a test'
#return y
print(f1(5))
When I ran the mypy command on this node, using , I got no output in
elp and
> suggestions I finally ran "brew doctor" which advised me to remove and
> update specific symlinks to Python3, which I did, and voila - it now works
> also devel version of Leo according to your instructions!
>
> Thanks a lot, you guys are awesome!
>
> Vili
aving mypy ignore
the type mismatch is perfectly fine as you said.
On Wednesday, March 3, 2021 at 1:22:44 PM UTC-5 Edward K. Ream wrote:
> On Wednesday, March 3, 2021 at 10:37:01 AM UTC-6 tbp1...@gmail.com wrote:
>
> Thanks for these comments. They inspired me to dig a little deeper in
There could be a special instance of p that plays the role of null, in that
it returns None when tested. Call it p_none. mypy would recognize it as
the same type as type(p) so it would be type safe, and p.__bool__ would
return False when tested if p were p_none. There would only need to be
There seems to be some possibility that the python3 that is invoked when
running
python3 -m ~/leo-editor/leo/core/runLeo.py
is not the same python3 that was used when Leo was installed (whether or
not that was done under an Anaconda installation I'm not sure). On top of
that, plain *python
Leo
On Thursday, February 25, 2021 at 9:51:30 AM UTC-5 Edward K. Ream wrote:
> On Thu, Feb 25, 2021 at 7:14 AM tbp1...@gmail.com
> wrote:
>
> This sounds similar in concept to the scheme I came up with for the
>> zettelkasten work. Any zettel node can contain re
This sounds similar in concept to the scheme I came up with for the
zettelkasten work. Any zettel node can contain references to others by
referring to their gnx. To make it work in a practical way required a
couple of scripts. One of these scripts inserted the gnx of the node to be
PR: #1826
https://github.com/leo-editor/leo-editor/pull/1741
On Monday, February 22, 2021 at 10:44:22 AM UTC-5 Edward K. Ream wrote:
> On Fri, Feb 19, 2021 at 10:53 AM tbp1...@gmail.com
> wrote:
>
>> I just found a JEdit colorizer code for Julia, and converted it using
&g
gt;
> On Monday, February 22, 2021 at 12:25:12 AM UTC+1, tbp1...@gmail.com
> wrote:
>>
>> No, no pip installation. The Leo code just needs to be located in the
>> site-packages subdirectory. Now Leo should run:
>>
>> python3.9 -m leo.core.runLeo
>>
>
ip3
> install ?
>
>
> On Sunday, February 21, 2021 at 11:58:44 PM UTC+1, tbp1...@gmail.com
> wrote:
>>
>> After downloading it, say to your *~/Downloads* directory or whatever is
>> like that on your Mac, unzip it. Within the unzipped directory tree there
>>
build wheels for leo which use PEP 517 and cannot be
> installed directly
>
> Tried with --upgrade, and sudo, and with sudo -H to which I was prompted.
>
>
> On Sunday, February 21, 2021 at 10:34:45 PM UTC+1, tbp1...@gmail.com
> wrote:
>>
>> That looks like a file pe
That looks like a file permissions issue, maybe. Try running with *sudo*.
Also, you haven't specified the branch to install. This way you would get
the "master" branch, which is not the one to get. You want "devel".
Here is the command I used the last time I installed from *devel* this way:
ith excellent programming skills and he also complained
> recently about problems with installing Leo on Mac. So, I gues I will wait
> for the next pip version of Leo anyway in order to use "Clone-Find-Parents"
> command.
>
>
> Br, Vili
>
> On Sunday, February 2
" directory and some compilation happens, and
> then automagically Leo just works by typing "leo" in terminal.
>
> I don't know how to achieve this with devel version of Leo from git.
>
> Vili
>
> On Sunday, February 21, 2021 at 3:36:24 PM UTC+1, tbp1...@gmail.c
/Users/vili/leo-editor/core/runLeo.py': [Errno 2] No such file or
> directory
>
> Now I have to go. I will try to figure it out later.
>
> BR, Vili
>
> On Sunday, February 21, 2021 at 2:18:59 PM UTC+1, tbp1...@gmail.com wrote:
>>
>> " python3 core\runLeo.py &q
" python3 core\runLeo.py " - of course, on MacOS that would be python3
core/runLeo.py.
On Sunday, February 21, 2021 at 8:14:26 AM UTC-5 tbp1...@gmail.com wrote:
> Let me add a little clarification here.
>
> When Edward writes " Installing git is no more difficult than
Let me add a little clarification here.
When Edward writes " Installing git is no more difficult than installing
any other program.", he meant but didn't say that you need to install the
*git* program on your computer before following his steps.
After you have gotten the latest version - in
I just found a JEdit colorizer code for Julia, and converted it using Leo's
Jedit2Py script button. It worked perfectly, so now we can have Leo
colorizing Julia files.
On Friday, February 19, 2021 at 12:10:08 AM UTC-5 tbp1...@gmail.com wrote:
> I've been prototyping new functional
I've been prototyping new functionality for Viewrendered3 that would allow
for non-python code to be executed. It's working, but it also has some
limitations. I'd like suggestions as to whether this functionality will be
worthwhile or whether it would be too limited. To execute code blocks,
Leo (which I installed under miniconda)
> was being launched with 3.9.
>
> Using this command, I was able to add the markdown library to 3.9 as well:
>
> ./python3.9 -m pip install markdown
>
> Works like a charm now.
>
> Thanks again.
>
>
> On Tuesday, February 9, 2
Just for fun, here is a very lightweight test runner I have used
sometimes. First, I define a decorator that prints the name of each test
function and its docstring when the test is called:
def self_printer(f):
def new_f(*args):
print()
print ('Test:', f.__name__)
It works for me :)
Most likely thing I can think of: You installed markdown with a different
Python installation than the one that launches Leo.
For example, on some Linux systems (and on my own Windows one), *python*
runs Python 2.7 while *python3* runs Python 3.8.
On Monday, February 8,
On Thursday, February 4, 2021 at 7:15:33 PM UTC-5 brian wrote:
> The dev has the same problem as 6.3. I did a diff between the dev and
> 6.3. The changes are trivial and are limited to the import part. The
> problem method is createDirectoryForFile. The createDirectoryForFile
> method has
a
> node. Here is what says
>
> Leo 6.3, master branch, build e46e9315f6
> Python 3.9.1, PyQt version 5.15
> Linux
> ---
>
> I'm running CentOS 7 with all the patches applied.
>
> How do I file a bug report? As
I just tried it on my Windows machine and didn't get your results. I got a
few messages about "unexpected indentation", but it didn't raise an
exception and exit. My installation:
Leo 6.4-devel, devel branch, build 1b431f4b7b
2020-12-31 09:26:52 -0500
Python 3.8.6, PyQt version 5.15.1
Windows
On Tuesday, February 2, 2021 at 7:08:58 AM UTC-5 Edward K. Ream wrote:
> I'm back from a two-week staycation, eager to work.
> [snip]
> - I am more comfortable with static type systems after studying rust. I'll
> experiment with mypy to check Leo's objects.
>
Remember that Python now has an
So there is a difference between us - I don't feel a need to do
note-taking, etc. in a browser tab. Fair enough.
On Monday, February 1, 2021 at 4:44:07 PM UTC-5 viktor@gmail.com wrote:
> tbp1...@gmail.com schrieb am Montag, 1. Februar 2021 um 05:21:52 UTC+1:
>
>> On Sunday
On Sunday, January 31, 2021 at 1:46:13 PM UTC-5 viktor@gmail.com wrote:
> tbp1...@gmail.com schrieb am Sonntag, 31. Januar 2021 um 17:22:29 UTC+1:
> [snip]
> OK, I misunderstood your question then - and - I guess I also did not
> stress enough, that I was referring *only* to t
is that it is possible to enjoy many of the core features of
Jupyter in Leo already. You, however, may want to do other things, things
that Jupyter does better. That's why I asked about your workflow.
On Sunday, January 31, 2021 at 10:37:41 AM UTC-5 viktor@gmail.com wrote:
> t
On Sunday, January 31, 2021 at 9:26:19 AM UTC-5 Edward K. Ream wrote:
> On Sun, Jan 31, 2021 at 5:40 AM Viktor Ransmayr
> wrote:
>
> >> I agree that Leo as a web app would have to be a fully functional
> product. For me the lure is the cool Leovue graphics. But python is my
> passion. Why
Viktor, could you say more about the workflow you are thinking of? For
myself so far, I am happy to keep Leo open in its own app outside a
browser. And I would prefer to avoid running a server on my system to
mediate between Leo and the browser. However, without a server, it's not
really
I noticed some error messages about the {{...}} paths in my little test
@path nodes. It seems that I shouldn't be putting fixed strings between
{{...}}. After correction, my @path node looks like this:
@path d:{{sep}}temp{{sep}}xxx-rst
The *rst3 *command correctly saved the file. Then I
This does not happen on my Windows machine using the current devel branch:
Leo 6.4-devel, devel branch, build 1b431f4b7b
2020-12-31 09:26:52 -0500
Python 3.8.6, PyQt version 5.15.1
Windows 10 AMD64 (build 10.0.19041) SP0
On Friday, January 22, 2021 at 10:50:52 AM UTC-5 Arjan wrote:
> I'm
On Friday, January 22, 2021 at 5:44:53 AM UTC-5 jkn wrote:
> When I put the nodes under an @path node, though, it worked as expected
>> on my Windows system:
>>
>> - @path {{d:}}{{sep}}{{temp}}{{sep}}{{xxx-rst}}
>>- @rst pathtest
>> - Node 1
>> - Node 2
>> Running the *rst3*
On Thursday, January 21, 2021 at 5:29:51 PM UTC-5 jkn wrote:
> On Thursday, January 21, 2021 at 5:41:58 PM UTC tbp1...@gmail.com wrote:
>
>> It works for me :) That is, the text of all the child nodes of the @rst
>> node gets included in the single rst file t
On Thursday, January 21, 2021 at 12:41:58 PM UTC-5 tbp1...@gmail.com wrote:
> ... The script looks like this:
>
> import os
>
> cmd = ('py -m sphinx -C '
> '-D master_doc=xxx-rst '
> '-D source_suffix=.txt '
> '-D html_theme=sphinx_rtd_theme ' # Omit for a default
It works for me :) That is, the text of all the child nodes of the @rst
node gets included in the single rst file that *rst3* outputs and the node
headlines become subtitles. However, you don't have to use a path
expression, even if it is in an @path node. You can use an ordinary path
for
For an @rst node, the *rst3* command adds a *.txt* extension to every
filename. Maybe there is a setting to change this, I don't know. Sphinx is
happy working with **.txt* files, as long as you tell it to in the Sphinx
configuration. If @rst is including the entire path in the file name,
Remember that you can expect to re-implement at least twice before you get
something really good...
On Tuesday, January 19, 2021 at 7:50:21 AM UTC-5 Edward K. Ream wrote:
>
>
> Implementing leoFind.py in leoInteg will require substantial inventions,
> regardless of whether leoInteg
601 - 700 of 813 matches
Mail list logo
