Re: Portable Python/Leo for Windows

On Wednesday, May 13, 2020 at 7:31:09 PM UTC-4, Thomas Passin wrote: > > Thanks, very cool! These expansion thingies are new to me. I used to use > 4dos and 4nt, but haven't done anything at all tricky with batch files > for ages. > > On Wednesday, May 13, 2020 at 11:18

Re: Portable Python/Leo for Windows

Thanks, very cool! These expansion thingies are new to me. I used to use 4dos and 4nt, but haven't done anything at all tricky with batch files for ages. On Wednesday, May 13, 2020 at 11:18:07 AM UTC-4, Matt Wilkie wrote: > > I did have to edit the batch file paths from f:\ to e:\ because the

Re: Portable Python/Leo for Windows

you would put a site-customize directory if you use one, and apparently occasional packages will use the directory during install or operation. On Monday, May 11, 2020 at 11:55:01 PM UTC-4, Thomas Passin wrote: > > There used to be a portable app type package for Python so that it could &g

Re: Portable Python/Leo for Windows

> On Mon, May 11, 2020 at 10:55 PM Thomas Passin > wrote: > >> There used to be a portable app type package for Python so that it could >> be run from a USB stick and used on different computers. >> > > I thought this was what Matt just did. What's the difference? &

Portable Python/Leo for Windows

There used to be a portable app type package for Python so that it could be run from a USB stick and used on different computers. But no longer. I thought it would be interesting to see what would be involved in setting one up. This is for Windows. I'm sure it could be adapted for Linux

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

During the long saga, someone - was it Matt? - suggested removing the credentials helper from git so that user/pw would be required for each push. I did that. Now that it's all working, I was able to restore the helper and I don't need to provide them each time. On Windows, here's the

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

that great since docutils isn't rendering it, but at least it displays as it was supposed to. On Friday, May 8, 2020 at 11:18:55 AM UTC-4, Thomas Passin wrote: > > On Friday, May 8, 2020 at 10:56:25 AM UTC-4, Edward K. Ream wrote: >> >> >> >> On Fri, May 8, 2020 a

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

On Friday, May 8, 2020 at 10:56:25 AM UTC-4, Edward K. Ream wrote: > > > > On Fri, May 8, 2020 at 8:49 AM Thomas Passin > wrote: > > After cruising through some of the settings for repo on Github, I see that >> there is a branch protection rule on the de

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

On Friday, May 8, 2020 at 2:36:47 AM UTC-4, Matt Wilkie wrote: > > Thomas I made some more Leo Editor org and member changes. Please try > pushing again, with a new file that doesn't already exist in the repo. > > -matt > I created a new branch tbp-test in the Leo repo. I fetched it and

Re: ENB: Qt-prototype is finished

Very nicely done! I would favor adapting prototype constructs into Leo. Any other way would mean that the new branches would be need to catch up to the rest of Leo as it evolves. Continual catch-up has been a problem for some other projects (more complicated than Leo, no doubt). It's

Re: Qt-prototype report and some thoughts about executeScript command

Do you think it would be feasible to simply copy the root of the tree to be operated on? Then the undo would entail pointing the tree's original parent to the copy and then redrawing. I don't know about copy performance (I suppose that a deep copy would be needed) on Leo nodes, but as a

Re: ENB: rethinking Model/View/Controller split in Leo

On Thursday, May 7, 2020 at 11:49:31 AM UTC-4, tfer wrote: > > Thanks Matt and Thomas, I'll look into that. It's not that I want to > avoid Zoom so much, I want to demonstrate some work flow stuff, (Windows > 10, some Powershell stuff, and It's virtual workspace), so that's why I > need to

Re: a portable Leo.exe, maybe

Yes, and I think you have to run it on a Mac to get a Mac version. For linux, I don't know how version-specific you need to be. On Thursday, May 7, 2020 at 11:26:46 AM UTC-4, Matt Wilkie wrote: > > This would have to be Windows only, wouldn't it? All the packagers I >> looked at recently

Re: a portable Leo.exe, maybe

This would have to be Windows only, wouldn't it? All the packagers I looked at recently could make a self-contained package for just one kind of OS. Of course, that's not a surprise! On Thursday, May 7, 2020 at 2:33:45 AM UTC-4, Matt Wilkie wrote: > > Hi Folks, > > I'm taking a run at

Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

Matt, thank you for the setting me up to contribute to the Leo repo. This finally got me past the problem with my password not getting me access. On my first attempt to push viewrendered3, after merging I got this error: Writing objects: 100% (117/117), 48.58 KiB | 3.04 MiB/s, done. Total

Re: ENB: rethinking Model/View/Controller split in Leo

Actually, Zoom does let you share your screen. The host can let any participant take control, and they can share their screen. On Wednesday, May 6, 2020 at 6:20:59 PM UTC-4, tfer wrote: > > > In a week or so, I'd like to do some teleconferencing with Edward, (not > Zoom, but something with the

Re: ENB: rethinking Model/View/Controller split in Leo

On Wednesday, May 6, 2020 at 1:26:08 PM UTC-4, Edward K. Ream wrote: > > On Wed, May 6, 2020 at 9:37 AM 'tfer' via leo-editor < > leo-e...@googlegroups.com > wrote: > > I've expressed before that I feel that the use of the word "clone", does >> not really capture what we are doing here, in fact,

Re: ENB: An important puzzle re Leo's decorators

The few times I've written decorators, I've always written the arguments as *args. That way avoids problems where inner methods/functions are called with/without self or default args. E.g.: # decorator REQUIRE_MAIN def REQUIRE_MAIN(procedure): def new_proc(*args): # args[0] would be

Re: ENB: rethinking Model/View/Controller split in Leo

I'm always in favor of good separation of interests. It can be hard to achieve in practice, and it's always helpful to be diligent about keeping one's eye on the ball. What I'm reading here sounds pretty interesting. About clones, we always talk about cloning nodes, but it seems to me that

Re: ENB: About Leo's outline redraw code

On Friday, May 1, 2020 at 1:30:17 PM UTC-4, vitalije wrote: > > As an example of the elegant code you can look at the returns > package. Quite often in Leo > None is used either as a return value from a function or as an argument to > the function.

Re: ENB: About Leo's outline redraw code

On Friday, May 1, 2020 at 12:54:53 PM UTC-4, vitalije wrote: > > On my machine, the outline loads in about two seconds. I'm happy with >> that - I don't see how a faster load time would matter. >> > > Well you may be right about this. Maybe it isn't the speed that matters so > much. > > But

Re: ENB: About Leo's outline redraw code

On Friday, May 1, 2020 at 11:09:10 AM UTC-4, vitalije wrote: > > Dear Edward, > I find that it was very difficult to discuss code improvement ideas with > you. The most noticeable road-block for such discussions was your habit of > not reading and therefore not understanding the idea. Of course

Re: Technical document writing using asciidoctor via Leo

On Tuesday, April 28, 2020 at 1:27:41 AM UTC-4, Austin(Xu) Wang wrote: > > Dear All, > > I'm switching from Markdown to Asciidoctor for writing documents. I'd like > to use Leo as the central part for orgenizing all the docs. > > There are a list of questions I'm going to explore. If you have

Re: Question related to 'Installing Leo with Git'?

I am going to reiterate here something I posted in another thread. If you want to use the git method (or indeed run from a downloaded unzipped archive), there is another way to set up your system besides virtual environments or pip install --editable. I do it this way because I have the

Re: Is it safe to run different instances of Leo on the same machine?

On Saturday, April 25, 2020 at 2:50:25 PM UTC-4, Viktor Ransmayr wrote: > > Hello Matt, > > This is a first response from my side, in order to provide you an > **initial** feedback! > > In other words, I might change my mind, if I wake up tomorrow morning - > and - will review this thread /

Re: Question related to 'Installing Leo with Git'?

As the footnoted reference says, If you install from Git, you can get the latest development versions. What it does not say is that the latest development version is usually not in the "master" branch of the git repository. It is usually in the "devel" branch. If you don't know Git a bit -

Re: Is it safe to run different instances of Leo on the same machine?

I've done it from time to time, sometimes by accident. Each instance of Leo will use the same configuration files, as your logs show. This means that the last instance to exit will be the one that may change these files, like the list of recent files. I have also noticed that if I have the

Re: Converting Pre-5.0 Leo files?

Glory Be! The external Python file I sent you imported like a charm. Cruising through it, it seems to be in order. 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

Re: Converting Pre-5.0 Leo files?

7c 2020-04-23 12:41:01 -0500 Python 3.8.0, PyQt version 5.12.7 Windows 10 AMD64 (build 10.0.18362) SP0 On Thursday, April 23, 2020 at 2:45:30 PM UTC-4, Thomas Passin wrote: > > I was able to read the file and recover the intended structure. And I > saved and re-opened it successfully. How

Re: Converting Pre-5.0 Leo files?

Here 'tis. On Thursday, April 23, 2020 at 3:22:17 PM UTC-4, Edward K. Ream wrote: > > > > On Thu, Apr 23, 2020 at 1:52 PM Thomas Passin > wrote: > >> Here's another one of the old files. >> > > Please send the external file. I need the external file to

Re: Converting Pre-5.0 Leo files?

Here's another one of the old files. The current "old" branch won't open this one at all. Here's the last part of the error message: File "d:\Tom\git\leo-editor\leo\core\leoAtFile.py", line 536, in readFileAtPosition at.read(p, force=force) File

Re: Converting Pre-5.0 Leo files?

I was able to read the file and recover the intended structure. And I saved and re-opened it successfully. However, after I saved the outline, it would not open in the devel branch version. Here's the (last part of the) error I got: File

Re: Converting Pre-5.0 Leo files?

Here's one that won't open. It raises scripting errors as it tries. On Thursday, April 23, 2020 at 6:35:54 AM UTC-4, Edward K. Ream wrote: > > On Wed, Apr 22, 2020 at 4:31 PM Thomas Passin > wrote: > > Is there a practical way I can convert these old Leo files? >> &

Converting Pre-5.0 Leo files?

I have some old, from version 4, Leo outlines. They won't open in Leo these days. I used to have a copy of Leo 4.7 that I could use, but I can't install that on my new computer because it wants PyQt4 and I can't get that for Python 2.7 any more (I keep a Python 2.7 installation just in case I

Re: Setting up Leo for web development and TEI XML

On Tuesday, April 21, 2020 at 3:20:17 PM UTC-4, Iohannes wrote: > > Oh, that is great. I did not know where to look for it but hopefully I > have found it. > I am a little bit still confused how all "@" work. But hopefully, I will > find it out :). > Thanks, > You can see how it works in the

Re: ENB: Dubious idea: multi-dimentional outlines

Here you go. I've included all of my zettel scripts. The one I mentioned is zettel-goto-node. On Tuesday, April 21, 2020 at 11:34:05 AM UTC-4, Edward K. Ream wrote: > > > > On Tue, Apr 21, 2020 at 9:41 AM Thomas Passin > wrote: > > You may not remember, but

Re: Viewrendered3 Updates

I really appreciate all these suggestions! Unfortunately none of them have lead to success, although I've learned a few things. Even after doing the unset credential.helper commands and creating a new remote, I get this: C:\repos\leo-editor>git push leo_origin_2 devel Username for

Re: ENB: Dubious idea: multi-dimentional outlines

On Tuesday, April 21, 2020 at 9:56:26 AM UTC-4, Edward K. Ream wrote: > > Innovation almost happens without a juicy problem. The problem that > inspired these thoughts was this: how can we associate unit tests with (the > code in) a Leo node? > [snip] > > Leo already has unl's (uniform node

Re: Where Leo shines for me

This organizing ability is one of Leo's strong points for me. Many text editors these days can show you a tree with functions or classes as the nodes. Many word processors will show you a creditable outline. But only Leo can do those things and also let you break up the material according

Re: Setting up Leo for web development and TEI XML

I've put them in the attached Leo outline. All of them should go under the @settings node in MyLeoSettings.Leo. Note that the two @button commands are specific to Windows. They could be done in Linux, of course, but the exact commands would be specific to each linux distro. Maybe someone

Re: Setting up Leo for web development and TEI XML

On Monday, April 20, 2020 at 8:11:46 AM UTC-4, Thomas Passin wrote: > > Continuing on ... > > (If there were some interest, I could enhance the plugin to collect all > the javascript in the subtree and send it to the browser. > I just enhanced the viewrendered3 plugin so tha

Re: Setting up Leo for web development and TEI XML

However, you may not need to do anything special, at least for starters. I just tried importing a very simple HTML file, and the importer broke it out into head, script, body, and image nodes. That's a very good start. I used the Files/Import Files/Import Any File menu Item. On Monday, April

Re: getting node name of script behind a button?

If you want to get a little more complicated, you could do this dance: 1. Write the script so that when it's run the first time, it rewrites the script node to define its name: p.b = f'script_name = {p.h}\n' + p.b 2. Run the script using CTRL-B. 3. There has to be some code to check to see if

Re: Viewrendered3 Updates

I already had the upstream origin configured. To follow your suggestions, I created a new one and deactivated the previous one. I still get the same results, and in thedialog to manage remotes, using the "Test Connection" button gave this: Unable to open connection: Host does not exist

Re: Setting up Leo for web development and TEI XML

On Monday, April 20, 2020 at 12:20:48 AM UTC-4, Iohannes wrote: > > Hi, a beginner here again. > > I would appreciate some advice on how to se tup Leo. I am no professional > programmer. I am doing research in humanities but I like to do some little > stuff here and there. > One of the more

Re: Setting up Leo for web development and TEI XML

On Monday, April 20, 2020 at 12:20:48 AM UTC-4, Iohannes wrote: > > Hi, a beginner here again. > > I would appreciate some advice on how to se tup Leo. I am no professional > programmer. I am doing research in humanities but I like to do some little > stuff here and there. > > - ideally also

Re: Setting up Leo for web development and TEI XML

On Monday, April 20, 2020 at 12:20:48 AM UTC-4, Iohannes wrote: > > Hi, a beginner here again. > > I would appreciate some advice on how to se tup Leo. I am no professional > programmer. I am doing research in humanities but I like to do some little > stuff here and there. > > - How to rename

Re: Setting up Leo for web development and TEI XML

Hi, @Iohannes, I can give some suggestions for some of your questions. You could use them as starting points. On Monday, April 20, 2020 at 12:20:48 AM UTC-4, Iohannes wrote: > > Hi, a beginner here again. > > I would appreciate some advice on how to se tup Leo. I am no professional >

Re: Is there any user-friendly installer for Leo?

On Monday, April 20, 2020 at 1:23:07 AM UTC-4, Matt Wilkie wrote: > > > >> What's more, if I set PYTHONPATH to point to my git clone location, the >> leo command launches Leo from there instead of from the standard >> install. Excellent - that's just what I would want. >> > > Cool, I didn't

Re: Is there any user-friendly installer for Leo?

On Sunday, April 19, 2020 at 8:37:38 PM UTC-4, Matt Wilkie wrote: > > In order for the bare command leo to work, the operating system has to >> know that it's a Python file and that it's supposed to open a Python file >> using Python. Sometimes this chain of identification doesn't get set up

Re: Pyzo as a live Leo explorer

On Sunday, April 19, 2020 at 7:59:58 PM UTC-4, tfer wrote: > > > On Sunday, April 19, 2020 at 6:16:54 PM UTC-4, Thomas Passin wrote: >> >> No, not IPython. >> > > As text has no vocal inflection, I don't now what you mean by this, do you > mean: > No, n

Re: Viewrendered3 Updates

On Sunday, April 19, 2020 at 8:45:19 PM UTC-4, Matt Wilkie wrote: > > Hmm. What happens with `git push` from console? (see tab button beside > [commit, diff, file tree, ...] in Git Extensions, or just from a regular > command prompt). Any error messages? > That pushes to my fork, but not

Re: Viewrendered3 Updates

Thanks, Matt! On Saturday, April 18, 2020 at 8:13:59 PM UTC-4, Matt Wilkie wrote: > > That is very inspiring Thomas! > I'm still stuck on pushing my changes to the Leo repo. Here's hoping you can help! Edward told me he's added me to Leo's contributors, but every attempt I've made to push a

Re: getting node name of script behind a button?

I don't know what the create-button script does, but if you want something quick and dirty for occasional use, you could embed the script's id and print that. The script's node identifier is p.gnx,so if you add lines to your script like id = 'TomP.20200419185110.1' g.es(id) it would identify

Re: Is there any user-friendly installer for Leo?

In order for the bare command leo to work, the operating system has to know that it's a Python file and that it's supposed to open a Python file using Python. Sometimes this chain of identification doesn't get set up right. It seems like that was the problem when you got this error message:

Re: Pyzo as a live Leo explorer

On Sunday, April 19, 2020 at 4:11:41 PM UTC-4, tfer wrote: > > Okay, I've made some progress. Turns out, I was erroneously assumed I was > in an IPython shell because it had 'magics', but it was just the idle > interpreter, (never spent much time in Idle). All it took was creating a > new

Re: Pyzo as a live Leo explorer

n running adds a lot of inspection stuff. > > On Saturday, April 18, 2020 at 6:41:37 PM UTC-4, Thomas Passin wrote: >> >> >> >> On Saturday, April 18, 2020 at 4:58:58 PM UTC-4, tfer wrote: >>> >>> Okay, I'm playing with this, getting interesting results

Re: Pyzo as a live Leo explorer

On Saturday, April 18, 2020 at 4:58:58 PM UTC-4, tfer wrote: > > Okay, I'm playing with this, getting interesting results: > [snip] > pip install pyzo > I installed Pyzo using the standalone installer. I don't know if that would make any difference in what you are doing or not. But at

Re: Pyzo as a live Leo explorer

th Ipython/Jupiter. On Wednesday, April 8, 2020 at 12:25:56 PM UTC-4, Thomas Passin wrote: > > > On Wednesday, April 8, 2020 at 11:37:18 AM UTC-4, Matt Wilkie wrote: >> >> Thanks for the extra detail Thomas. >> >> Something like this function in runLeo.py >> <

Re: Quiet time is over

Possibly fitting in with this, I have just discovered SourceTrails, a static code analyzer that works with Python code (as well as Java, C, and C++): https://www.sourcetrail.com/ Sourcetrails can work with quite a few editor/IDEs by means of an intermediate server, including Sublime Text,

Re: Query about promote-child-bodies script

On Saturday, April 18, 2020 at 5:41:36 AM UTC-4, lewis wrote: > > After using a leo script_A to convert a list of lines into separate nodes > for each line of p.b. > I have a script_B that reads child nodes, and copies all the body text > lines back to the parent. It is based on @button

Viewrendered3 Updates

I have updated the VR3 plugin with some bug fixes and minor changes, and more significantly by adding a new @image directive. Edward (@ekr) had suggested this, and after some reflection I decided to try it out. The new directive requires a url: @image url-to-image where the url can be

Re: Leo command line options are ignored

It can get trickier if you have more than one python installation, as I do. I keep python 2.7, since there are still a few older programs I may run that don't run with python 3+. It turns out that the 2.7 installation added its directories to the system path, and the 3.8 installation did not.

Re: No vim or pyzo bridges for Leo

I think you are looking at the wrong level. You are writing in terms of implementation, but what is ti about vim that you expect to do in Leo, and why do think Leo has something to offer an experienced vim user? Note that I'm writing as a non-vim user, so my ideas about its usefulness are

Re: Reproducible computational science

t; This a hard problem and I was just suggesting that an 'out of the box' > solution using something like Leo might be worth considering. > > Kind regards, > Brad > > > > On Tuesday, April 7, 2020 at 6:14:14 PM UTC-6, Thomas Passin wrote: >> >> It's interest

Re: No vim or pyzo bridges for Leo

Hi, Gar, On Wednesday, April 8, 2020 at 11:58:27 AM UTC-4, gar wrote: > > > I have to use very outdated syntax highlight schemes for most languages I > use! pygments are claimed to be supported > but works with python only. > Colorizing works with other languages if you mark them with an

Re: Pyzo as a live Leo explorer

On Wednesday, April 8, 2020 at 11:37:18 AM UTC-4, Matt Wilkie wrote: > > Thanks for the extra detail Thomas. > > Something like this function in runLeo.py > > to add command line argument might be used to invoke no-docks:

Re: Reproducible computational science

It's interesting to me, anyway. Could you talk about why you haven't found Jupyter notebooks to be satisfactory? On other threads we have been discussing whether Leo, with the Viewrendered3 plugin, might be able to do much of what Jupyter does, and have some advantages besides. Your question

Re: Pyzo as a live Leo explorer

The steps I posted earlier give you a running copy of Leo, and access to some to Leo's objects in Pyzo's Workspace pane, but the interactive shell pane doesn't accept input. I suppose it's waiting for Leo to terminate. I have found a simpler set of steps that launch Leo, let you see many more

Re: Pyzo as a live Leo explorer

On Monday, April 6, 2020 at 7:29:57 PM UTC-4, Matt Wilkie wrote: > > Happy Monday discovery: > > Pyzo's workspace feature can be used to interactively explore Leo's > modules, functions, classes, methods and defined variables in real time. > This is so cool > It is very cool, and your steps

Re: Creation of Leo's Documentation locally in 6.1b1?

On Saturday, April 4, 2020 at 3:40:15 PM UTC-4, Viktor Ransmayr wrote: > > Hello Edward, hello Matt, > > Am Dienstag, 29. Oktober 2019 14:56:33 UTC+1 schrieb Edward K. Ream: >> >> On Tue, Oct 29, 2019 at 3:44 AM Viktor Ransmayr >> wrote: >> >>> >>> Should it be possible to create a local

Re: Sorting mystery

On Friday, April 3, 2020 at 3:07:14 PM UTC-4, Rob wrote: > > This is not a Leo problem. However, there a lot of very smart people here > who might have some insights into this. > > I want to name files in an intuitive way so that Windows (and other apps > like Adobe Lightroom) sort them

Re: iLeo not working

It's not going to work with Python 3.8 either. There's been some change to the asnyc API that Tornado hasn't adjusted to. I believe there is a workaround, but I don't have the reference handy. py38 -m leo.core.runLeo --ipython ... File

Re: What's next, continued

On Thursday, April 2, 2020 at 2:27:42 PM UTC-4, Offray Vladimir Luna Cárdenas wrote: > > > I for sure want live coding. It is not a theoretical desire. I have > experience it in Pharo and recently in (Python's powered music system) > FoxDot. They operate similar to Crtl+B and not as you

Re: What's next, continued

On Thursday, April 2, 2020 at 12:36:33 PM UTC-4, Offray Vladimir Luna Cárdenas wrote: > > And I would like to see live coding for Leo. I just don't how that's going > to happen. > > Maybe Leo should think in kind of a minimal server or something that > tracks code changes and updates

Re: For Thomas: C++ problems in pyqt

obably remove them in a future version, since we won't need many of them, but a few probably need to stay. So there will be more work ahead on this issue, but maybe this fix will take care of most of the cases. On Wednesday, April 1, 2020 at 9:43:33 PM UTC-4, Thomas Passin wrote: > > Accord

Re: For Thomas: C++ problems in pyqt

:04 PM UTC-4, Thomas Passin wrote: > > Thanks, that looks like it could be relevant. > > On Wednesday, April 1, 2020 at 6:37:34 PM UTC-4, Edward K. Ream wrote: >> >> Here's the link. I found it while cleaning out my bookmarks :-) >> >> http://enki-editor.org/2014/

Re: Thomas, the fix branch fixes vr3.py

Edward, if you retrieved this file before about 9:30 PM Eastern, please get it again. I found a bug where the line h = c.hash() in store_layout had been removed during my merge. It needs to be there. On Wednesday, April 1, 2020 at 8:00:27 PM UTC-4, Thomas Passin wrote: > > I merged the

Re: For Thomas: C++ problems in pyqt

Thanks, that looks like it could be relevant. On Wednesday, April 1, 2020 at 6:37:34 PM UTC-4, Edward K. Ream wrote: > > Here's the link. I found it while cleaning out my bookmarks :-) > > http://enki-editor.org/2014/08/23/Pyqt_mem_mgmt.html > > Maybe it will help find the memory problems in

Re: Thomas, the fix branch fixes vr3.py

I merged the files. For some reason I couldn't push my changes upstream to the "fix" branch. Although I was logged in to Github, it said it couldn't authenticate. So I pushed the changes to the devel branch of my own fork and sent a PR. On Wednesday, April 1, 2020 at 6:31:35 PM UTC-4,

Re: warning viewrender3.py plugin has been commited with unresolved conflicts.

Right, and Edward has already asked me to clear this up. On Wednesday, April 1, 2020 at 11:38:11 AM UTC-4, vitalije wrote: > > Title tells everything. While executing unit tests, two are failing: check > syntax of all files and pluginTestCase for viewrender3. > > Vitalije > -- You received

Re: FYI: pylint-leo-rc-ref.txt disables two new pylint tests

It's really a comprehension vs brevity thing, and a matter of personal style. Removing the else gives shorter code, which is *usually* more clear. But without the *else*, you have to *infer* its virtual presence, and that interferes with comprehension. I'm not consistent about this, myself.

Re: Tom, please fix vr3 in devel

OK, I'll take a run at it. It can be difficult when you have a lot of changes that are mostly whitespace and style. I messed one up that way recently, too. On Wednesday, April 1, 2020 at 6:34:20 AM UTC-4, Edward K. Ream wrote: > > Somehow it contains many conflict markers from a git merge. >

Re: Tom, please fix vr3 in devel

It's always annoying when there are a lot of whitespace and style changes. I'll see about it. (For the benefit of anyone else who is wondering what this is about, this commit tried to remove a lot of complaints from pylint about whitespace and other sylistic nits that had build up over the

Re: Jupyter vs Leo + VR3

On Tuesday, March 31, 2020 at 6:42:01 PM UTC-4, Edward K. Ream wrote: > As you say, at present the ipynb.do_cell method (in importers/ipynb.py) > doesn't save much. It should be easy to save more, if you would like that. > Easy, perhaps, but I would go slowly, because we need to look at how

Re: font size shrank

On Tuesday, March 31, 2020 at 2:36:38 PM UTC-4, andyjim wrote: > > All was well this morning, but just now when I came back to Leo I find the > font size in the bodies of all nodes has shrunk to unreadably small size. > Text in the node headings is ok. This is only for one of six files I have

Re: font size shrank

On Tuesday, March 31, 2020 at 2:36:38 PM UTC-4, andyjim wrote: > > All was well this morning, but just now when I came back to Leo I find the > font size in the bodies of all nodes has shrunk to unreadably small size. > Text in the node headings is ok. This is only for one of six files I have

Re: Leo and Jupyter

On Tuesday, March 31, 2020 at 11:44:23 AM UTC-4, tfer wrote: > > There is another option we could consider, rather than full juypter stuff, > just add an Ipython console tab to the log pane. Though not as sexy as > Juypter, it has most of its guts, is embed-able, and has a qt-console >

Re: Jupyter vs Leo + VR3

On Tuesday, March 31, 2020 at 9:28:01 AM UTC-4, Edward K. Ream wrote: > > On Tue, Mar 31, 2020 at 8:19 AM Thomas Passin > wrote: > > Thomas, seems like we agree on points 1 through 3. > > >> 4. In the (unlikely?) event that people want to use both Leo and > jupyter,

Re: Jupyter vs Leo + VR3

On Tuesday, March 31, 2020 at 7:24:52 AM UTC-4, Edward K. Ream wrote: > > Thomas, this post is an indirect response to some of your recent remarks. > There is some chance I understand them now ;-) > It's hard to grasp some of these things until you get time to work with VR3 for a while. I

Re: Leo and Jupyter

On Monday, March 30, 2020 at 1:04:12 PM UTC-4, Edward K. Ream wrote: > > On Mon, Mar 30, 2020 at 11:08 AM Thomas Passin wrote: > > > There are at least four ways that Leo could be used with Jupyter: > > All four look like the hard way. I tried the hard way several times

Re: Leo and Jupyter

On Monday, March 30, 2020 at 12:15:44 PM UTC-4, Thomas Passin wrote: > > > The questions are: what benefit could be gotten by interfacing Leo and > Jupyter, and how complicated would it be? > It seems to me that it would be essential to be able to embed images, interactive plot

Re: Leo and Jupyter

Leo Notebooks are easy to imagine, but they would never gain traction because Jupyter is too widespread already. On Monday, March 30, 2020 at 12:13:04 PM UTC-4, Thomas Passin wrote: > On Monday, March 30, 2020 at 12:08:15 PM UTC-4, Thomas Passin wrote: >> >> On Monday, March 30

Re: Leo and Jupyter

On Monday, March 30, 2020 at 12:08:15 PM UTC-4, Thomas Passin wrote: > > On Monday, March 30, 2020 at 12:06:47 PM UTC-4, Thomas Passin wrote: >> >> >> This thread is for discussion about how or whether Leo might be able to >> play with Jupyter. >> >>

Re: Leo and Jupyter

On Monday, March 30, 2020 at 12:06:47 PM UTC-4, Thomas Passin wrote: > > > This thread is for discussion about how or whether Leo might be able to > play with Jupyter. > > I think there are basically four general ways that Leo could interact with > Leo. I'll put them in m

Leo and Jupyter

Users of Leo who also know about Jupyter and Jupyter notebooks sometimes see a resemblance. Now that the Viewrendered3 plugin is working (though still a beta version), it is possible to render code and the resulting text and plots in the same node, which looks even more like Jupyter. Leo

Re: About VR3, holoviews and bokeh

On Monday, March 30, 2020 at 8:12:25 AM UTC-4, Thomas Passin wrote: > On Monday, March 30, 2020 at 6:48:29 AM UTC-4, Edward K. Ream wrote: >> >> Thomas Passin and I have been discussing his vr3 plugin in private. This >> is a great plugin. Our conversation deserves to be pu

Re: About VR3, holoviews and bokeh

And it turns out that it's just as easy to work with Seaborn, On Monday, March 30, 2020 at 6:48:29 AM UTC-4, Edward K. Ream wrote: > > Thomas Passin and I have been discussing his vr3 plugin in private. This > is a great plugin. Our conversation deserves to be public. > >

Re: About VR3, holoviews and bokeh

On Monday, March 30, 2020 at 6:48:29 AM UTC-4, Edward K. Ream wrote: > > Thomas Passin and I have been discussing his vr3 plugin in private. This > is a great plugin. Our conversation deserves to be public. > > *Holoview and bokeh* > > Holoviews and bokeh are both imp

Re: About VR3, holoviews and bokeh

On Monday, March 30, 2020 at 6:48:29 AM UTC-4, Edward K. Ream wrote: > > Thomas Passin and I have been discussing his vr3 plugin in private. This > is a great plugin. Our conversation deserves to be public. > > Here I am going to discuss what I think I know about vr3 and its

<    7   8   9   10   11   12   13   14   15   >