Re: why does goto-prev/next-visible command change focus to body?

Your change of focus isn't happening for me. Neither using the arrow keys nor running goto-next-visible changed the focus to the body. Looking at the code for the method c.endEditing. c.endEditing() calls qtree.endEditLabel(), and that kicks out the headline editor but without changing focu

Re: weirdness when trying to enable a new (or any?) plugin

Good find! You know, I don't even have a "python3" on my Windows path. If you had used the "py" launcher I think it would have worked right away. I didn't realize you weren't. If there have been multiple installations of Python and you don't use "py", lord knows what you will get. In a non-ve

Re: weirdness when trying to enable a new (or any?) plugin

The only things I can think of at this point are to look again to see if that dll file is actually present somewhere, and to try to import the web engine directly in an interpreter session (IOW, not importing from LeoQt) , e.g., from PyQt6 import QtWebEngineWidgets QWebEngineView = QtWebEngineW

Re: weirdness when trying to enable a new (or any?) plugin

Don't hesitate to delete all those files. Or do what I used to do. Instead of deleting them, move them to some other folder. You can always copy them back. I used to do that when Leo could use both Qt5 and Qt6. I probably should have used venvs but instead I moved all the Qt6 files out for t

Re: weirdness when trying to enable a new (or any?) plugin

I'm no venv expert, that's for sure. I *think* that packages installed into a venv can be symlinked from the non-venv installation if they are the same version. Better try to check that, though. It sounds like that what's happening in your case. It didn't seem to in mine. All a mystery. I

Re: weirdness when trying to enable a new (or any?) plugin

Freewin falls back to using a QTextBrowser if a QWebEngineView isn't present. That only affects the rendered view, not the editor view. The QTextBrowser's rendering is limited compared with the QWebEngineView but that won't really matter for most nodes. I have removed all the PyQt* files from

Re: ENB: About @jupytext and @language jupytext

Thanks for testing! On Tuesday, November 5, 2024 at 5:00:12 AM UTC-5 viktor@gmail.com wrote: > Hello Edward, hello Thomas, > > Edward K. Ream schrieb am Samstag, 2. November 2024 um 14:55:59 UTC+1: > > This Engineering Notebook post discusses how I created *@jupytext* and > its companion, *@

Re: weirdness when trying to enable a new (or any?) plugin

That seems like just what I did. You might look at the Qt files in Python's Lib\site-packages in the venv and see if they are symlinked to the files in the main (non-vm) install. I don't know when files in a new VM get symlinked and when they don't. If they are symlinked then I only have thre

Re: weirdness when trying to enable a new (or any?) plugin

After a kernel update on my Linux Mint VM just now, I got the same error - no PyQt6-WebEngine. Upgrading the PyQt6-x packages didn't fix the error. I installed using requirements.txt into a venv and running in that venv VR3 finds the QWebEngine and runs. On Monday, November 4, 2024 at 6:51:53

Re: weirdness when trying to enable a new (or any?) plugin

I thought PyQt6-QScintilla is required now (don't know why). There are a few apparent mismatches in versions, like PyQt6 6.7.1 PyQt6-Qt6 6.7.3 I have differences too, only not the same ones as yours. I don't understand why, but my system has been w

Re: weirdness when trying to enable a new (or any?) plugin

On Monday, November 4, 2024 at 6:51:53 AM UTC-5 jkn wrote: Hmm, slightly separate point, but now I am trying to replicate things (enabling viewrendered3) on my Windows machine... I am getting a Windows Error popup: ... Qt6WebEngineCore.dll was not found... Leo itself doesn't have an error fro

Re: weirdness when trying to enable a new (or any?) plugin

On Sunday, November 3, 2024 at 5:55:10 PM UTC-5 jkn wrote: Anyway - after putting 'freewin.py' in myLeoSettings.leo (and installing QtWebEngineView for PyQt6 - interestingly VR3 does not seem to give a warning if this is not installed) - I seem to be making progress, both with VR3 and with Fre

Re: weirdness when trying to enable a new (or any?) plugin

On Sunday, November 3, 2024 at 5:06:35 PM UTC-5 jkn wrote: The .pyc files in my plugins/ directory are extremely old, I am sure they predate anything in myLeoSettings.leo ... All .pyc files with Python 3.x go into a *__pycache__* folder (I don't know if this started with Python 3.0 or with a

Re: weirdness when trying to enable a new (or any?) plugin

On Sunday, November 3, 2024 at 3:50:44 PM UTC-5 jkn wrote: I feel like I am being a bit dim here... I'm trying to enable the freewin plugin (I am actually also trying viewrendered/viewrendered3, but 'backed off' to freewin, because I seem to be having fundamental plugin issues. You have to i

Re: New Script To Render @jupytext files With VR3

On Thursday, October 31, 2024 at 10:29:31 PM UTC-4 iamap...@gmail.com wrote: Thank you, Thomas. The script works. The command will create a new node below your @jupytext tree and will select it. But I don't quite understand why you need to do this? Why do we need a new node? Is it becaus

Re: New Script To Render @jupytext files With VR3

On Friday, November 1, 2024 at 4:11:43 PM UTC-4 Edward K. Ream wrote: On Wed, Oct 30, 2024 at 6:40 PM Thomas Passin wrote: Now that we have a more stable import format for @jupytext nodes, I redid my script to produce a version that renders the file with VR3. Very cool. I see intermixed

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

On Friday, November 1, 2024 at 5:52:08 AM UTC-4 jkn wrote: Actually, assuming that the getattr() call *can* return a value in some circumstances, mumble mumble stylesheets, then presumably this is the fix? def weight_modifier(item: Item, param: str) -> None: #

Re: @jupytext: final touches

I'm not sure about you doing anything "wrong", but try importing the .ipynb file from Leo's *File/Import Files/Import Any File menu*. It's been working well for me. On Friday, November 1, 2024 at 4:37:50 AM UTC-4 lewis wrote: > I am trying out @jupytext but having some issues. > > Leo is buil

Re: New Script To Render @jupytext files With VR3

I create a new node for rendering because VR3 understands how to render markdown with the @language directives but the @jupytext tree isn't markdown. If the leading comment signs were removed and the code sections fenced then VR3 would be able to render the entire tree, but not the way things s

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

On Thursday, October 31, 2024 at 6:22:20 PM UTC-4 jkn wrote: yes, that's nice to know, thanks for the tip. I got the values from the PyQt documentation ... but I should have realised from the fact that QFont.Weight is an Enum, that it would have names. Fancy new Python features ... bring back

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

to use for bold, not 75. It's an integer, not a string. On Thursday, October 31, 2024 at 9:23:44 AM UTC-4 jkn wrote: it is the getting of the argument, from eg: # part of declutter-pattern WEIGHT 700 or ? WEIGHT Bold # as per documentation => "arg = 700" that is not working,

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

;>>> >>>>>>> I had a quick look at the way it's used, and I find it hard to >>>>>>> understand. I can see the intention but the layers of indirection make >>>>>>> it >>>>>>> hard. Say the pattern in myLeoSettings is *

Re: New Script To Render @jupytext files With VR3

i = 0 if is_code else 2 cells.append(line[i:]) if is_prefix: cells.append(MD_LITERAL_FENCE) body = '\n'.join(cells) vr3_jupytext_node = JUPYTER_POSITION.insertAfter() vr3_jupytext_node.h = 'Rendering for ' + jupy_file[1] vr3_ju

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

;> it. None of those strings exist of attributes of QFont, so the default >>>> always comes back, which is 75. >>>> >>>> Anyway, 700 is the value to use for bold, not 75. It's an integer, not >>>> a string. >>>> >>

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

;>> or ? >>> WEIGHT Bold # as per documentation >>> >>> => "arg = 700" >>> >>> that is not working, I think. >>> >>> On Thursday, October 31, 2024 at 1:15:28 PM UTC tbp1...@gmail.com wrote: >>> >>&

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

=> "arg = 700" > > that is not working, I think. > > On Thursday, October 31, 2024 at 1:15:28 PM UTC tbp1...@gmail.com wrote: > >> On Thursday, October 31, 2024 at 7:45:05 AM UTC-4 Thomas Passin wrote: >> >> Either of these work in the sense of ex

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

Either of these work in the sense of executing without producing an error. I haven't tried applying the font to see the results: from leo.core.leoQt import QtGui, QtWidgets QFont = QtGui.QFont newfont = QFont('Georgia') newfont.setWeight(QFont.Weight.Bold) # or newfont.setWeight(700) On Wedne

Re: tree-declutter 'WEIGHT bold' no longer working after upgrading to PyQt6

On Thursday, October 31, 2024 at 7:45:05 AM UTC-4 Thomas Passin wrote: Either of these work in the sense of executing without producing an error. I haven't tried applying the font to see the results: from leo.core.leoQt import QtGui, QtWidgets QFont = QtGui.QFont newfont = QFont(&#x

Re: ENB: Why deleting cell markup won't work

On Wednesday, October 30, 2024 at 7:44:08 AM UTC-4 Edward K. Ream wrote: This Engineering Notebook post explains why removing and restoring cell markup can not work reliably. The idea seems tempting. Why put up with all that cruft? But this scheme has a fatal flaw: there is no *dead easy* way

Re: @jupytext improvements ready for review

On Wednesday, October 30, 2024 at 6:51:00 AM UTC-4 Edward K. Ream wrote: I do have two suggestions, though, both trivial to implement. 1. Only use the first 6 words of the first line for the headline, the way my script did. The new* jtm.compute_headline* method does a much better job of com

Re: @jupytext improvements ready for review

On Wednesday, October 30, 2024 at 6:51:00 AM UTC-4 Edward K. Ream wrote: 2. Put an @nocolor directive at the top of each markdown cell. I'm not going to do this because @nocolor suppresses *all* coloring. Then add @color to code cells. They are the ones that should be colorized. -- You re

Re: @jupytext improvements ready for review

I tried importing the two files I've been using for my experiments and they both seem right. I didn't try round-tripping the notebook files, and I didn't look closely to see if there were any extra blank lines inserted. I do have two suggestions, though, both trivial to implement. 1. Only use

Re: ENB: Enhance @jupytext with Thomas's script

On Tuesday, October 29, 2024 at 10:02:39 AM UTC-4 Edward K. Ream wrote: On Tue, Oct 29, 2024 at 8:11 AM Thomas Passin wrote: I would like to make one more push for eliminating the '#' characters that comment out each and every line of a juyptext line. Here is snippet from my

Re: ENB: Enhance @jupytext with Thomas's script

On Tuesday, October 29, 2024 at 6:39:20 AM UTC-4 Edward K. Ream wrote: The fruitful collaboration with Thomas continues. This Engineering Notebook post discusses adapting Thomas's prototype script to enhance how Leo handles @jupytext nodes. Some nodes of the hierarchy may be missing, but that'

Re: Jupytext - Script To Split Into Child Nodes

On Tuesday, October 29, 2024 at 5:16:13 AM UTC-4 Edward K. Ream wrote: Spoiler: Thomas's script should enhance @jupytext rather than become a separate command. Splitting the @jupytext node into an outline can be done with complete safety. I agree. And doing so would put the @juptext imports

Re: ENB: Enhance @jupytext with Thomas's script

I would like to make one more push for eliminating the '#' characters that comment out each and every line of a juyptext line. They can be put back when the file is saved. They do nothing for a Leo user except ad visual clutter, and the possibility for error if someone accidentally removes or

Re: ENB: Enhance @jupytext with Thomas's script

On Tuesday, October 29, 2024 at 6:39:20 AM UTC-4 Edward K. Ream wrote: The fruitful collaboration with Thomas continues. This Engineering Notebook post discusses adapting Thomas's prototype script to enhance how Leo handles @jupytext nodes. This enhancement: - will be rock solid. - can cover

Re: Jupytext - Script To Split Into Child Nodes

I think we are roughly in agreement. My plan is to look only at the indentation of the first line after the cell marker. Any other lines in the cell with heading levels won't - by definition - change the indentation of the cell because a cell can only have one indentation level. And cells can

Re: Jupytext - Script To Split Into Child Nodes

On Monday, October 28, 2024 at 8:27:28 PM UTC-4 Edward K. Ream wrote: On Monday, October 28, 2024 at 6:27:34 PM UTC-5 Thomas wrote: Wait! The imported file in the @jupytext node is already in juyptext format, not JSON. This hint made everything clear. - The @jupytext node must contain *all

Re: Jupytext - Script To Split Into Child Nodes

On Monday, October 28, 2024 at 6:39:50 PM UTC-4 Edward K. Ream wrote: Alright. I'm on it. Here's my plan: - Start with the markdown importer. Oops. That won't work directly. I forgot that .ipynb files are json, not plain text. Thomas's script parses the json directly, but it is probably bes

Re: Jupytext - Script To Split Into Child Nodes

rd K. Ream wrote: > On Mon, Oct 28, 2024 at 11:31 AM Thomas Passin wrote: > >> I need some guidance on edge cases before I can get the script to indent >> beyond one level. >> > > These are all good questions. I was planning to work on this script, but > I'll

Re: Jupytext - Script To Split Into Child Nodes

I need some guidance on edge cases before I can get the script to indent beyond one level. 1. If the first cell has no markdown header level, it should only be indented one level, right? There's nowhere else for it to go. 2. If the first cell has a markdown header level > 1, the indentation sh

Re: Fixed: Leo's help-for-layouts command

Thanks! Please include what layout you are using, whether the issue happens immediately after an outline has been loaded, or otherwise when you notice it. Also include, if you would, what help command you tried and how you dispatched it (minibuffer, menu, etc.). As you can imagine, I did a lo

Re: Fixed: Leo's help-for-layouts command

On Monday, October 28, 2024 at 3:20:40 AM UTC-4 viktor@gmail.com wrote: I tried to do a re-rest of the latest changes - and - noticed that there is a surprising interaction b/w the ~ final ~ layout system implementation & the help system. *NO help info is not displayed at all until I expli

Re: Fixed: Leo's help-for-layouts command

t-name" but it hasn't. On Monday, October 28, 2024 at 8:27:27 AM UTC-4 viktor@gmail.com wrote: > Hello Edward, > > Edward K. Ream schrieb am Montag, 28. Oktober 2024 um 12:45:00 UTC+1: > > On Mon, Oct 28, 2024 at 6:29 AM Thomas Passin wrote: > > The problem is

Re: Fixed: Leo's help-for-layouts command

ently?) renamed to - @string qt-*style*-name = None # Qt Gui settings" I see I should have quoted more from the post. On Monday, October 28, 2024 at 7:45:00 AM UTC-4 Edward K. Ream wrote: On Mon, Oct 28, 2024 at 6:29 AM Thomas Passin wrote: The problem is that we don't activate VR/VR3

Re: Fixed: Leo's help-for-layouts command

The problem is that we don't activate VR/VR3 at first because the user might not want to see it and it's pretty distracting when you don't want it. Until the first time VR3 is shown in a layout, it's quiescent. The same thing probably happens for the F11 command. I thought I had checked all th

Re: Jupytext - Script To Split Into Child Nodes

On Monday, October 28, 2024 at 5:00:23 AM UTC-4 Edward K. Ream wrote: On Sun, Oct 27, 2024 at 4:21 PM Thomas Passin wrote: Here is a script that will take an @jupytext tree and split it out into child nodes, one node per cell. To use, make a script button for it, select a @jupytext node

Re: Jupytext - Script To Split Into Child Nodes

On Monday, October 28, 2024 at 3:43:23 AM UTC-4 iamap...@gmail.com wrote: Thanks Thomas, It works great! Although for `jupyter lab`, its ToC is displayed according to the markdown level in the document, I think it is not a big problem to extract nodes according to cells like you did, anyway, n

Jupytext - Script To Split Into Child Nodes

Here is a script that will take an @jupytext tree and split it out into child nodes, one node per cell. To use, make a script button for it, select a @jupytext node, and run the script. The script tries to create reasonable headlines for the nodes but of course it can't be perfect. Please try

Re: Leo's jupytext code works!

On Thursday, October 24, 2024 at 7:14:08 PM UTC-4 Thomas Passin wrote: A very small addition to VR3's code will allow the notebook to be rendered, and even executed. Here's an example of VR3 rendering a converted jupyter notebook (I did by hand what that "small addition to VR

Re: Tip - Finding Leo's Documentation More Easily

he window, underneath the minibuffer. > > Jake > > On Oct 26, 2024, at 12:06 PM, Thomas Passin wrote: > >  > > I keep an outline in which I'm slowly building up bits of information > about Leo (and Linux, Python, whatever). I wanted to find the table of > Leo'

Tip - Finding Leo's Documentation More Easily

I keep an outline in which I'm slowly building up bits of information about Leo (and Linux, Python, whatever). I wanted to find the table of Leo's hooks today. I didn't want to fish around the various Leo files and web pages trying to find it. Instead, I knew I had it in my outline so I sear

Re: Engineering Notebook - Jupytext The Leonine Way

I see that I forgot that the Python code in a Jupytext file is already uncommented (shucks, I knew that yesterday!) So we do get syntax highlighting as is. All the rest still applies. On Saturday, October 26, 2024 at 9:03:34 AM UTC-4 Thomas Passin wrote: > This is a long post so I'm p

Engineering Notebook - Jupytext The Leonine Way

This is a long post so I'm putting a summary at the start. 1. Leo can provide a very good way for a user to create and edit Juptyer notebooks. 2. The exploratory work for @jupytext files does not provide a proper Leonine experience. 3. The usual Leo approach is weak when it comes to working with

Re: Leo's jupytext code works!

Don't get too set on the way @jupytext works right now. It's not actually very Leonistic. We can do better. I will talk about why I say that and how to do better in an upcoming post. On Saturday, October 26, 2024 at 12:42:12 AM UTC-4 iamap...@gmail.com wrote: > Well, yes, execution ability w

Re: Head up: PR #4121 (in devel) may cause problems

I tested all the layouts in a Linux VM too and they all worked as intended. All except the one where I had a typo. Are you sure that didn't happen to you? Which layout had you specified, and what did you get? On Friday, October 25, 2024 at 5:07:12 PM UTC-4 Edward K. Ream wrote: > On Friday,

Re: Leo's jupytext code works!

Well, yes, execution ability will be limited, that's right. VR3 won't know about magics, and all the needed libraries will have to be imported in the outline. Also graphics that Jupyter would embed won't work. So execution capabilities would be limited, but there will be some outlines that coul

Re: Head up: PR #4121 (in devel) may cause problems

On Friday, October 25, 2024 at 5:47:47 PM UTC-4 Edward K. Ream wrote: On Fri, Oct 25, 2024 at 4:33 PM Thomas Passin wrote: I tested all the layouts in a Linux VM too and they all worked as intended. All except the one where I had a typo. Are you sure that didn't happen to you?

Re: Head up: PR #4121 (in devel) may cause problems

y into devel. If VR doesn't show itself one might get fooled into thinking that the wrong layout had been loaded - depending on the layout, of course. On Friday, October 25, 2024 at 3:04:24 PM UTC-4 Thomas Passin wrote: > Please coordinate changes with me. > > On Friday, October 25,

Re: Head up: PR #4121 (in devel) may cause problems

What layout is in your settings? On Friday, October 25, 2024 at 2:59:42 PM UTC-4 Edward K. Ream wrote: > I encountered strange behavior after merging #4121 into devel. *Leo > opened with a different layout than the one my settings specified.* The > workaround was to execute the 'layout-quadrant

Re: Head up: PR #4121 (in devel) may cause problems

Please coordinate changes with me. On Friday, October 25, 2024 at 2:59:42 PM UTC-4 Edward K. Ream wrote: > I encountered strange behavior after merging #4121 into devel. *Leo > opened with a different layout than the one my settings specified.* The > workaround was to execute the 'layout-quadra

Re: Leo's jupytext code works!

I wonder if all the work with the percent-encoded files couldn't be done with StringIO in-memory streams. On Thursday, October 24, 2024 at 11:57:07 AM UTC-4 Edward K. Ream wrote: > On Thursday, October 24, 2024 at 8:14:20 AM UTC-5 Edward K. Ream wrote: > > > PR #4119

Re: Leo's jupytext code works!

eam wrote: > On Thu, Oct 24, 2024 at 12:53 PM Thomas Passin wrote: > >> " Leo now *deletes* the paired .py files when writing .ipynb files. " >> > > I'm learning about jupytext and jupyter options. Stay tuned. > > Edward > -- You received this

Re: Leo's jupytext code works!

-percent-format> has a .py extension" - from https://jupytext.readthedocs.io/en/latest/ but whatever they are called, they are what I meant. On Thursday, October 24, 2024 at 1:35:16 PM UTC-4 Edward K. Ream wrote: > On Thu, Oct 24, 2024 at 11:47 AM Thomas Passin wrote: > >> I

Images In Leo Nodes - A Way To Make Them Work

I think many of us would like to be able to stick images into Leo nodes. It's easy to insert one. You get the text cursor for the insertion point, give it the image URL, and call insertImage(). The editor component will let you cut and paste the image without any other code being written. Fo

Re: Fixing PR #4111

ested this case, BTW, and the code works as intended. PR coming up very soon. On Wednesday, October 23, 2024 at 1:11:14 PM UTC-4 Edward K. Ream wrote: > On Wed, Oct 23, 2024 at 9:31 AM Thomas Passin wrote: > >> We do need to be able to load a layout if the setting for the start

Re: Fixing PR #4111

On Wednesday, October 23, 2024 at 10:43:46 AM UTC-4 viktor@gmail.com wrote: I believe the default setting is 'legacy' coming from "leoSettings.leo". Ha! You are so right. We better remember to change that if we eliminate the "legacy" layout. -- You received this message because you ar

Re: Fixing PR #4111

t (I think) with no slot for VR/VR3. It's probably better to be explicit about which layout will be used, I think). On Wednesday, October 23, 2024 at 8:19:36 AM UTC-4 Thomas Passin wrote: > On Wednesday, October 23, 2024 at 7:01:07 AM UTC-4 viktor@gmail.com > wrote: >

Re: Fixing PR #4111

On Wednesday, October 23, 2024 at 7:01:07 AM UTC-4 viktor@gmail.com wrote: Hello Edward & Thomas, Edward K. Ream schrieb am Dienstag, 22. Oktober 2024 um 18:12:05 UTC+2: I performed an initial test using the current 'devel' branch in my Debian VM. - Here are my notes: ### * Start with '

Re: ChatGPT As A Helper - A Transcript

I had to make sure it was active if a layout needed it (even if not visible) so it would open in the right slot in the layout. I put in a test for whether VR3 had been enabled or not, and changed the layout's slot name it it was/was not. That all worked, but maybe I made a mistake and didn't

Re: ChatGPT As A Helper - A Transcript

After that, I'll create a new PR with the code to collect all the layout docstrings to support a help-for-layouts command, and then we should be good to go for 6.82. On Tuesday, October 22, 2024 at 10:00:02 AM UTC-4 Edward K. Ream wrote: > On Tue, Oct 22, 2024 at 8:48 AM Thomas Passin wrot

Re: ChatGPT As A Helper - A Transcript

Hah! I see it's been done. Good! On Tuesday, October 22, 2024 at 8:28:10 AM UTC-4 Thomas Passin wrote: > On Tuesday, October 22, 2024 at 4:19:07 AM UTC-4 Edward K. Ream wrote: > > On Mon, Oct 21, 2024 at 11:07 PM Thomas Passin wrote: > > I've been trying to use Chat

Re: ChatGPT As A Helper - A Transcript

On Tuesday, October 22, 2024 at 4:19:07 AM UTC-4 Edward K. Ream wrote: On Mon, Oct 21, 2024 at 11:07 PM Thomas Passin wrote: I've been trying to use ChatGPT to get help on actual problems... Impressive transcript! Hehe, now can you get back to finishing Leo's layouts? There'

ChatGPT As A Helper - A Transcript

I've been trying to use ChatGPT to get help on actual problems that I didn't solve by using Internet search, or I wanted a more focused look at some particular issue. I've started to find it to be a real help - sometimes - but you have to set it up right, be patient, and keep shepherding it ba

Re: ENB: The first prototype for #4117: .ipynb support

On Monday, October 21, 2024 at 4:04:26 PM UTC-4 Edward K. Ream wrote: On Mon, Oct 21, 2024 at 2:56 PM Thomas Passin wrote: On Monday, October 21, 2024 at 3:38:29 PM UTC-4 Thomas Passin wrote: I just took a quick look at the jupyter extension(s) for VSCodium/VSStudio. It's very impre

Re: ENB: The first prototype for #4117: .ipynb support

On Monday, October 21, 2024 at 3:38:29 PM UTC-4 Thomas Passin wrote: I just took a quick look at the jupyter extension(s) for VSCodium/VSStudio. It's very impressive and very easy to read. I don't know why I would use the Jupyter inbrowser interface I used to use (some time ago; I&#

Re: ENB: The first prototype for #4117: .ipynb support

I just took a quick look at the jupyter extension(s) for VSCodium/VSStudio. It's very impressive and very easy to read. I don't know why I would use the Jupyter inbrowser interface I used to use (some time ago; I'm very much not updated about Jupyter). What it lacks and sorely needs, of course,

Re: ENB: Re-designing Leo's IPython bridge

More and more I am thinking that we should give up the idea of round-tripping between Leo and Jupyter. What you have written goes in that direction. Leo would be the primary authoring tool. From time to time a user can reload in Jupyter and see if the results are what was intended. That's ho

Re: ENB: Re-designing Leo's IPython bridge

On Monday, October 21, 2024 at 8:54:45 AM UTC-4 Edward K. Ream wrote: I'll investigate making Jupyter a client of leoserver only as a last resort. I think it should be the other way around - Leo would act as a client of a Jupyter server. Most of the real work happens in the server anyway, do

Re: ENB: Re-designing Leo's IPython bridge

How do you see using Leo with jupyter files? Jupytext has shown one way to get to a more textual representation. How would you deal with generated output, especially graphics? Would you want to run code from within Leo? How do you want to deal with magics? Or do you want just to do strictly

Re: Launching Leo when SageMath starts (Ubuntu)

mix RsT and Python code together and execute and render it with VR3. A screen shot is attached. On Sunday, October 20, 2024 at 7:18:25 PM UTC-4 Edward K. Ream wrote: > On Sun, Oct 20, 2024 at 3:02 PM Thomas Passin wrote: > > > EKR: Getting [SageMath's] plot statement to show t

Re: Logseq

That looks very interesting. It has some commonality with a zettelkasten, specifically the crosslinking between blocks, and the idea that the blocks should or can be focused on a limited topic. The querying system is pretty cool (if I were setting it up I might have tried for a more SQL-like

Re: Launching Leo when SageMath starts (Ubuntu)

On Thursday, October 17, 2024 at 1:55:27 PM UTC-4 Edward K. Ream wrote: import sage.all as sage from sage.all import Integer, plot y = sage.circle( (Integer(0),Integer(0)), Integer(1), rgbcolor=(Integer(1),Integer(1),Integer(0))) print(y) The print statement works, but neither of the fol

Re: ENB: Thought experiments re IPython

On Sunday, October 20, 2024 at 2:17:13 PM UTC-4 Edward K. Ream wrote: Imo, this scenario is infeasible and unwise. I am definitely no longer tempted by Sirens. There you go, the value of creating scenarios! -- You received this message because you are subscribed to the Google Groups "leo-

Re: Discuss: retire valuespace and jingarender plugins?

I think that valuespace must have been written for someone's very idiosycratic way of working. I would say that if the author wants to update it and keep using it, let him do the work. Even if Leo removes it, it's easy enough to keep using it outside Leo's plugin tree. I see that stringlist is

Re: ENB: Thought experiments re IPython

That's very interesting. The Jupyter ecosystem is expanding so fast that there is always something new. I don't actually use Jupyter-* so I'm not in touch with it at all. I always think I should be using Jupyter but I don't do much work these days that would make much use of it. On Sunday, Oc

Re: ENB: Thought experiments re IPython

I think you may be a little hasty here. Also, IPython is not the same as Sage even if Sage uses IPython under the cover (I'm not completely sure it does), and even if the standard Sage REPL looks like a console. So I've been think about Sage. Some of this may also apply to IPython, but maybe n

Re: ENB: Re-designing Leo's IPython bridge

I think that a good approach would be to come up with several use-cases or scenarios of how someone would actually use a hybrid Leo-IPython system. It's no different that the case of Jupyter or sage. I stopped supporting Jupyter notebooks in VR3 for the reason that I couldn't come up with one,

Re: When Does c.commandsDict Get Populated?

On Thursday, October 17, 2024 at 9:18:25 PM UTC-4 Edward K. Ream wrote: On Thu, Oct 17, 2024 at 5:35 PM Thomas Passin wrote: I wanted to use c.doCommandByName) during the DynamicWindow code that creates the initial layout but the command was not available and the length of c.commandsDict was

When Does c.commandsDict Get Populated?

I wanted to use c.doCommandByName) during the DynamicWindow code that creates the initial layout but the command was not available and the length of c.commandsDict was 0. When during outline creation does the dictionary get populated? -- You received this message because you are subscribed to

Re: Suppose I want to create a directory and a file in it....?

On Thursday, October 17, 2024 at 1:06:41 PM UTC-4 jkn wrote: As a slight aside, if I had not edited the node bodies, would you have expected the directories to then be created upon a write? There seems to be some sort of cache logic going on, but I am a bit unsure. One thing I know. You hav

Re: Suppose I want to create a directory and a file in it....?

I would be very suspicious of that "@leo" directory name. Would you repeat your tests but with a normal directory name (i.e., one without an "@" character)? On Thursday, October 17, 2024 at 10:39:46 AM UTC-4 jkn wrote: > Ah, interesting. I will post these results (on Windows, FWIW) in any case.

Re: Suppose I want to create a directory and a file in it....?

Funny. I just tried it before I posted and it did create the file and the inbetween directories at the end of the path. I'm on Windows and your path looks like Linux but I wouldn't think that would make a difference. I don't know what the @all is supposed to do so I have no opinion as to whet

Re: Suppose I want to create a directory and a file in it....?

Did you mean the setting @bool create_nonexistent_directories = True? I don't remember ever creating a directory without an @file at the end of it. You need to have a node for a file (it doesn't need to have any content) and save the outline before Leo will create the directory(s). Leo will cre

Re: Installing Leo in wsl Ubuntu-23.04

Wow, what a trek! Thank you for pulling all this together for us. And most of it will apply to any Ubuntu install, not just on WSL. On Wednesday, October 16, 2024 at 6:00:05 PM UTC-4 lewis wrote: > Here is a summary procedure on running Leo on wsl Ubuntu-24.04 and some > installation issues E

Re: Leo 6.8.2 coming soon. Please test devel

On Wednesday, October 16, 2024 at 3:38:54 PM UTC-4 viktor@gmail.com wrote: Hello Thomas, tbp1...@gmail.com schrieb am Mittwoch, 16. Oktober 2024 um 21:11:27 UTC+2: On Wednesday, October 16, 2024 at 3:00:08 PM UTC-4 viktor@gmail.com wrote: I did check out this setting now, found out

Re: Leo 6.8.2 coming soon. Please test devel

On Wednesday, October 16, 2024 at 3:00:08 PM UTC-4 viktor@gmail.com wrote: I did check out this setting now, found out that the values are almost identical to the 'layout command' names - as well as - I now also understand, why 'legacy' is the default layout ;-) Thanks a lot for your sup

Re: Leo 6.8.2 coming soon. Please test devel

On Wednesday, October 16, 2024 at 11:46:23 AM UTC-4 viktor@gmail.com wrote: Hello Thomas, tbp1...@gmail.com schrieb am Mittwoch, 16. Oktober 2024 um 15:50:16 UTC+2: ... layout-restore-default should restore the layout prescribed by the "qt-layout-name" setting, whatever it is. I tested

Re: Leo 6.8.2 coming soon. Please test devel

On Wednesday, October 16, 2024 at 9:14:05 AM UTC-4 viktor@gmail.com wrote: Hello Edward & Thomas, Viktor Ransmayr schrieb am Montag, 14. Oktober 2024 um 16:37:56 UTC+2: However these new test reveals the following about the layout commands: - layout-legacy == layout-quadrant == layout-

  1   2   3   4   5   6   7   8   9   10   >