Re: Another vitrectomy

Rest, heal! On Thursday, June 27, 2024 at 8:44:49 AM UTC-4 Edward K. Ream wrote: > I had a second vitrectomy of my right eye yesterday. The surgery went > well, but as before I will mostly be lying on my tummy for the next week. > > As a result, I'll delay 6.8.0 for another week. > > Edward >

Re: Hex File Snooper

e editor to work with your >> graphics card driver. >> >> >> On Thursday, June 13, 2024 at 8:45:01 PM UTC+1 tbp1...@gmail.com wrote: >> >>> After reading the link, I see I never got near anything like TECO. >>> >>> On Thursday, June 13, 2024 at

Re: Hex File Snooper

The original IBM PC was a quick-and-dirty design; performance was not a goal. FORTH is an opposite: Simplicity and flexibility are at the heart of its design, with carefully considered access to assembly language where required for performance or access to bare metal. The design requires

Re: Hex File Snooper

TECO for the PDP/8 was available under OS/8. The Wikipedia article on TECO is a nice summary. There you can find links to Web pages on TECO, including one by the originatoer of TECO and the GitHub repository for TECOC, a reimplementation in C

Re: Hex File Snooper

The TECO text editor was designed to edit files that were too large to fit in memory. I used TECO on a PDP8/e minicomputer; the 8/e used 12-bit words; memory was addressed in 128-word pages and 4096-word fields. The original implementation of Emacs was a set of "editor macros" written in

Re: I just had successful eye surgury

Heal, heal! On Thursday, March 28, 2024 at 4:03:52 PM UTC-4 Edward K. Ream wrote: > A vitrectomy > of > > the rt eye. I'll be limited in what I

Some humor

A message that applies to Leo and to other tools for literate programming: *"I don't want self-documenting code. I want self-coding documentation." * I found it after yet another occasional stroll through the catalog of calligraphic buttons of Nancy Lebovitz . She

Re: Quick steps on how I got Leo working on Windows 11

On Saturday, October 14, 2023 at 10:01:44 AM UTC-4 tbp1...@gmail.com wrote: I'd say this is how to get it installed using Anaconda, which apparently is not the same as using Python from python.org. For one thing, using python.org you don't have to install build tools to build pyqt5 (and note

Re: ENB: Ahas re paste-retaining-clones

On Sunday, August 13, 2023 at 5:31:16 AM UTC-4 Edward K. Ream wrote: Today is my 74th birthday. This Engineering Notebook post is my birthday present to myself. Have the happiest of birthdays. Thank you for working on your birthday and giving a gift to us all. -- You received this message

Re: ChatGPT Helpful In Translating Tables

On Thursday, June 22, 2023 at 11:22:20 AM UTC-4 tbp1...@gmail.com wrote: Even copying selected text out of a pdf file can be unpleasant. Often there will be no newlines, so words may run together when they were visually separated by a line break. Yes, indeed. Part of my day job involves

Re: ChatGPT Helpful In Translating Tables

On Sunday, June 18, 2023 at 11:06:30 PM UTC-4 tbp1...@gmail.com wrote: Very thoughtful piece by Jon Udell - Why LLM-assisted table transformation is a big deal . In my day job, I have to pull useful

Re: Pyspread - a spreadsheet where each cell can be a Python expression

On Tuesday, May 2, 2023 at 1:04:27 PM UTC-4 jkn wrote: There was a much older 'python in a spreadsheet' program, created by Resolver Systems. I followed it with interest, they tried to create a commercial product out of it but failed. That product used IronPython - an alternate implementation

Re: Leo 6.7.3 coming soon

On Monday, April 10, 2023 at 8:04:23 AM UTC-4 Edward K. Ream wrote: The fix appears to be straightforward, but it points out the folly of rushing to release major changes. If it is difficult for you, who know know Leo's code base so well, to keep in mind the complex interactions of that code

Re: Eye surgery tommorrow

The surgery appears to have gone well. The eye is blurry, but apparently that's normal. I'll see my eye doc later today. Best wishes! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails

Re: Pydantic - Type Hints For Validating Data

It does sound interesting. It even supports "custom" (user-defined) types. A plug-in for Pydantic supports Hypothesis , «a Python library for creating unit tests which are simpler to write and more powerful when run, finding edge cases in your

Re: New Leo "Package" File Format?

Now this is interesting! I wasn't considering huge image files, most just "ordinary" ones like photos, screenshots, or graphs that would be common images to want to include with, for example, a markdown document. I'll read up on your links. Thanks! A consideration that didn't occur to me

Re: New Leo "Package" File Format?

On Sunday, April 2, 2023 at 3:55:31 PM UTC-4 tbp1...@gmail.com wrote: It seems to me that the main challenge would be for Leo to know just what to have in the package. External files would be easy, but for example image files - how to know about them could be a real challenge. I'm thinking

Re: New Leo "Package" File Format?

On Saturday, April 1, 2023 at 10:06:06 PM UTC-4 mys...@gmail.com wrote: Having a zip file of all file assets would work as well with some implementation of a VFS by the program utilizing it I presume. Given use of the appropriate codec, Zip files are easily packed or unpacked. The zlib

Re: New Leo "Package" File Format?

I have seen this function referred to as "Pack and Go" in other software that is widely used - SolidWorks, AutoCAD for starters. On Wednesday, March 29, 2023 at 1:48:09 PM UTC-4 tbp1...@gmail.com wrote: > There is a perennial problem when one wants to give a Leo outline to > someone else.

Re: Programming By Contract for Python

Down the rabbit hole we go: Hypothesis looks worth a look. I know that some time back, I posted a message with links on Hypothesis and Pydantic. I haven't had time to explore them. In case the links are of use in the current dive down the rabbit

Leo package as published on test.pypi.org

I was looking for a pypy package of other software whose next release that has been in stuck in Alpha for a long time, and I ended up searching test.pypy.org , which is a repository for testing the publishing of Python packages. I found Leo there, but the Leo package

Re: OT? Beware of ChatGPT

Thanks for your comments. Imo, we have every right to consider the need to address manipulation by machines employing AI. Period :-) Yes, but I am academically-minded, and I expect to argue my case - because I do not expect to be believed unless I present a sound argument. -- You received

Re: OT? Beware of ChatGPT

Bear with me. What follows is Not Brief. Understanding and deployment of the current wave of AI require understanding of two works of The Twentieth Century. One is Kurt Gödel's Incompleteness Theorems. The other is Alfred Korzybski's General Semantics, as explained by S. I. Hayakawa.

Re: PyScript - Real Python In The Browser

An article on change coming with an upcoming update to the Dart language mentions that there is as yet no standard for garbage collection for WebAssembly. A group working on that has been chartered

Re: Leo deployment on Windows - past story, current story

apply to every user by editing the shortcut's properties, and replacing the *C:\username* in the *Target* field with *%HOMEPATH% *. %HOMEPATH% is a Windows environment variable that is evaluated when the shortcut is used rather than at the time of its creation. On Saturday, May 22, 2021 at 11:18:

Re: Repairing Windows System Files

On Sunday, June 12, 2022 at 3:35:17 PM UTC-4 tbp1...@gmail.com wrote: > You cannot get help on, e.g., "/cleanup-image", or even learn that it > exists, unless you prefix the help command with the "/online" . It seems > that dism can do so many things that the help system had to become >

Re: Repairing Windows System Files

On Sunday, June 12, 2022 at 9:26:35 AM UTC-4 David Szent-Györgyi wrote: Links of interest: > Repair a Windows Image > <https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image>; > > includes dism usage for checking whether an i

Re: Repairing Windows System Files

On Sunday, June 12, 2022 at 10:03:54 AM UTC-4 tbp1...@gmail.com wrote: > The help text for dism is mostly unintelligible to ordinary computer > users. You would have to know a lot of Microsoft-specific OS details to > make sense of most of it. The only help command likely to be helpful for >

Re: Please upvote Thomas's gf4 project

> > Youngsters have no idea what programming life was like in the "horse and > buggy" days 40 or 50 years ago: > > - Feeble hardware. > - Feeble programming tools: We worked in assembler or C. > No git, python, numpy, matplotlib and leo. > - No internet! No google, github and online

Re: Repairing Windows System Files

The terminology used with Microsoft's *dism* gives specific new meanings to terms widely used in broader contexts. Keep in mind these specific meanings: WIM file a "Windows image" file, used for deployment of Windows Vista and more recent versions of Windows; extension .wim VHD and VHDX files

Re: Repairing Windows System Files

On Saturday, June 4, 2022 at 5:57:21 PM UTC-4 tbp1...@gmail.com wrote: > I don't know when to prefer one over another. I run sfc first, perhaps > because it's easier to remember the command line. If problems are found > and claimed to be fixed, it's probably good to repeat the scan. > > I

Re: Why specs matter (On The Two Types Of Developers)

Rereading that "Dive into Mark" posting again after many years, with my US State's primary election coming tomorrow, my thoughts go in another direction: I think of parallels with respect to the law. For "a**holes" read "lawyers". For "morons" read "legislators". Reading Tom's distinction

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: > For more straightforward scripting engine uses, there's always Lua, though > the >> fork of Lua done to implement a JIT <http://luajit.org> trails the main >> implementat

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 5:18:15 PM UTC-5 tbp1...@gmail.com wrote: > On Monday, January 17, 2022 at 12:57:12 PM UTC-5 David Szent-Györgyi wrote: > >> Jython support for Python3 is planned >> <https://www.jython.org/jython-3-mvp> and roadmapped >> <https:

Re: Managing Python 2.7 Code In Leo

On Monday, January 17, 2022 at 6:01:43 AM UTC-5 Edward K. Ream wrote: > On Sun, Jan 16, 2022 at 3:08 PM tbp1...@gmail.com > wrote: > >> The project is a Tomcat web application that uses mixed java and Jython. > > > VSCode probably allows you to use python 2 for some projects. I am not >

Re: Personal take-aways from a rust video

The earlier edition that I saw doesn't give descriptions of the algorithms. Its descriptions of the data structures might be of interest. On Thursday, November 4, 2021 at 9:39:39 AM UTC-4 Edward K. Ream wrote: > On Wed, Nov 3, 2021 at 10:40 AM David Szent-Györgyi >

Re: Personal take-aways from a rust video

On Sunday, October 31, 2021 at 9:22:11 AM UTC-4 tbp1...@gmail.com wrote: > Very large collections are best thought of a graphs, IMO, because there > are usually many types of connections between them - depending of course on > the type and intended use of the entries. However, treelike

Re: Wow: AlphaFold .ipynb and Google Colab

On Wednesday, September 15, 2021 at 7:44:42 AM UTC-4 Edward K. Ream wrote: > Namely the Nobelist Albert Szent-Györgyi. > > The National Library of Medicine of the National Institutes of Health has a section of its

Re: Wow: AlphaFold .ipynb and Google Colab

AlphaFold is an extraordinary advance in the speed of the development of knowledge. Compare the rapidity of the understanding of the structure of COV-2 with the decades of labor required in the 1950s and 1960s for determination of the structure of myosin, the protein that is the largest

Re: Wow: AlphaFold .ipynb and Google Colab

My day job is technical support for basic research in life science, and abuts drug discovery, which is targeted work. Below is a note that I sent to my colleagues at the end of 2020, when last winter's COVID outbreaks were at a terrible high. --- note begins --- This is really interesting

Re: ENB: Converting unit tests for @shadow

For data that is generated by hand or by plugins that are not centrally controlled, and for tests that are difficult to write, would the thoroughness of property-based testing be relevant? I wrote about that some time back.

Re: Discuss: don't support Qt6 for Leo 6.4 final?

Qt 6.2, which is planned to be the first QT6 release that supports "all widely-used Qt add-on modules", is scheduled for release at the end of September. Its first beta was released on 6th July. See the entry on the Qt Developers' blog . Note for

Re: Python project delays changes to annotations

Edward writes: > I'm not worried. A few searches/replaces would likely do the trick. > That's good to hear. That tells me that you are sure that you can follow as mypy adapts to the changes that follow PEP 649. What interests me is that the Python development community has not settled on a

Re: Python project delays changes to annotations

>From the article: > "a Python Enhancement Proposal (PEP) was created to postpone their > evaluation until they were needed. The PEP-described behavior was set to > become the default in the upcoming Python 3.10 release, but that is not to > be; the postponement of evaluation by default has

Python project delays changes to annotations

This was published a couple of weeks ago, on 9th June, but it is likely to be current as of this date (26th June). It is of interest to Leo's developers and other programmers who annotate their Python code with typing information: The following excerpt begins "When and how to evaluate Python

Re: Good Monospaced Programmer's Font

The Wikipedia article on the Croscore fonts also mentions the Noto fonts : «Noto is a font family comprising over 100 individual fonts, which are together designed to cover all the scripts encoded in the Unicode standard. As of October 2016, Noto

Re: Good Monospaced Programmer's Font

Cousine is one of the Chrome OS core fonts, "Croscore fonts". Further font suggestions from the Wikipedia article on the Croscore fonts : Arimo (sans serif) - metrically compatible with Arial; Tinos

Re: Good Monospaced Programmer's Font

Cousine's designer is a professional with decades of experience. https://en.wikipedia.org/wiki/Steve_Matteson -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Good Monospaced Programmer's Font

More about Cousine: «Cousine is an open-source monospaced typeface designed by Steve Matteson and available for free through Google Fonts. It was designed to be metrically compatible with Courier New. Cousine is available in normal, italic, bold and bold italic styles. . . . SUGGESTED FONT

Does it make sense to spend much effort supporting 32-bit Windows, or 32-bit installations on 64-bit Windows?

>From Wikipedia's article on Windows 10 : «Starting with Windows 10 version 2004, Microsoft will require new OEM devices to use 64-bit processors, and will therefore cease the distribution of x86 (32-bit) variants of Windows 10 via

Anaconda 3.8 supports use of earlier releases of Python3

>From the documentation for Version 3.8 of the Anaconda distribution: Conda treats Python the same as any other package, so it is easy to manage and update multiple installations. Anaconda supports Python 2.7,

Leo deployment on Windows - past story, current story

I've written of the need to discuss the deployment stories on Windows, macOS, various Unix distributions, various Linux distributions. Before this discussion begins, one must consider that there are multiple

Re: Location of 'leoserver.py' & 'leoclient.py' in Leo's directory structure?

On Thursday, May 20, 2021 at 1:39:06 PM UTC-4 tbp1...@gmail.com wrote: > In my view, Leo *is* a 3rd party python package and should be installable > via pip. It is true that some Linux systems will tinker with the > directories, paths, etc and want you to install certain packages using >

Re: Tools of Interest: Hypothesis and Pydantic for Property-based Testing

The Overview page for Pydantic offers the following Rationale , which makes me think that it might be of interest to Leo's users and Leo's developers: «So *pydantic* uses some cool new language features, but why should I actually go and use

Re: Tools of Interest: Hypothesis and Pydantic for Property-based Testing

The Overview page for Pydantic offers the following Rationale , which makes me think that it might be of interest to Leo's users and Leo's developers: «So *pydantic* uses some cool new language features, but why should I actually go and use

Re: Tools of Interest: Hypothesis and Pydantic for Property-based Testing

*dataclasses integration *As well as BaseModel, *pydantic* provides a dataclass <https://pydantic-docs.helpmanual.io/usage/dataclasses/> decorator which creates (almost) vanilla python dataclasses with input data parsing and validation.» On Sunday, April 25, 2021 at 8:18:57 AM UTC

Tools of Interest: Hypothesis and Pydantic for Property-based Testing

These links might be of interest to Edward and others developing Python code, including Leo. First, a praise of property-based testing , with examples that differentiate it from example-based testing. Second, Hypothesis, «a

Re: [ctlug] M$ Joy

On Sunday, April 11, 2021 at 4:14:30 AM UTC-4 Edward K. Ream wrote: > > 1. Those who are planning major writing projects would be well advised to > make a serious study of the strengths and weakness of the major contenders, > including Jupyter, LaTeX, reStructuredText, and Leo. And yes, it

Re: David Szent-Györgyi: Please send an example .leo file

I apologize for the delay in digging this up. I've shared a Dropbox link with your edreamleo gmail com email address. The link is to a shared folder that at present contains a Zip archive with a couple of Leo files and WSF files - enough to open the Leo file. As the Leo file shows, I use

Using MacPorts to deploy Leo on macOS computers

Has anyone taken a recent look at MacPorts for deploying Leo? I know that using Homebrew to install Leo is the current recommendation. Homebrew has for years installed in */usr/local* on Intel Macs, and is now forced by Apple's tightening of access to that folder to install in */opt/homebrew*

Re: Discuss: remove @root?

referenced VBScript file and JScript file in the WSF file that I save. If I could make either of the single-LEO-file scheme work or the one-LEO-file-for-library-and-one-LEO-file-per-WSF-file schemed work, I could abandon the @root directive. On Saturday, February 27, 2021 at 1:19:28 PM UTC-5

Re: Discuss: remove @root?

Would you like to have a copy of the LEO file that contains the repository? You could see you my set-up. On Saturday, February 27, 2021 at 11:47:19 AM UTC-5 Edward K. Ream wrote: > On Thu, Feb 25, 2021 at 11:30 PM David Szent-Györgyi > wrote: > >> Leo is your project, you prov

Re: Discuss: remove @root?

Leo is your project, you provide free access to the fruits of your labor, if you're going to remote @root that's your decision, but it may cause me to ask questions I need answered if I am to preserve access to work that I've done. I've written about my use of Leo 4.3: it served as an easily

Re: ENB: Are huge Leo outlines possible?

On Wednesday, December 9, 2020 at 10:11:01 AM UTC-5 tbp1...@gmail.com wrote: > Ah, the pdp-8, a trip down memory lane. I used an 8i extensively in the > early 70s, but did not make the acquaintance of TECO. After looking it up > on Wikipedia, I' m glad I didn't. Remember how 3 ascii

Re: ENB: Are huge Leo outlines possible?

On Wednesday, December 9, 2020 at 10:30:54 AM UTC-5 Edward K. Ream wrote: > Yes, and those considerations have nothing to do with teco :-) > Leo doesn't need the engineering underlying TECO - fortunately, it doesn't have to work on an architecture of segmented memory - but editing text files

Re: ENB: Are huge Leo outlines possible?

On Saturday, October 24, 2020 at 1:07:15 PM UTC-4 Edward K. Ream wrote: > On Sat, Oct 24, 2020 at 11:53 AM Thomas Passin wrote: > >> Remembering back to long ago when we only had 640k of RAM at the most, >> there were editors that kept three screens of data in memory at once - the >> current

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

Edward writes: The great advantage Qt has (or had) over Tk was in the appearance of text. > Has Tk improved in that regard? > My guess is that tkinter as shipped with Python 3.6.8 and 3.7.7 and 3.8.2 would need careful testing. The macOS interface via Tcl/Tk is undergoing work - at present,

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

Edward writes: > > Thanks for this update. Vitalije recently created a prototype in Tk, so > there is actually some code available. > > The great advantage Qt has (or had) over Tk was in the appearance of text. > Has Tk improved in that regard? > Answer for Windows: work has been done. See

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

On Monday, May 4, 2020 at 8:23:17 AM UTC-4, Edward K. Ream wrote: > > Leo does not support a tk gui. It hasn't for at least a decade. See > leoPlugins.leo#Plugins-->Gui. > > It's possible to run tk code from Leo, but that is another matter entirely. > The Leo distributions had a virtue that is

Re: Org Brain

I believe that open source software ought to be guided by the desires of the developers. I also believe that it does no harm to provide feedback in the hope of broadening the goals of those developers. I'm sticking my neck out here, commenting on code and tools that I haven't written and

Re: ENB: Why I think keyword args are benign

On Tuesday, April 24, 2018 at 8:38:37 AM UTC-4, Edward K. Ream wrote: > > > It looks like json.dumps may have problems with p.v.unknownAttributes > fields. > > Again, not a gotcha, but something must be done. > Have you had time to look into AXON as a better-for-the-purpose alternative to

Re: Python 2?

On Sunday, March 11, 2018 at 7:19:24 PM UTC-4, Edward K. Ream wrote: > > I have just created #800: Replace pickle with json everywhere in Leo > . > > Imo, this is a high priority item. It should have been done long ago. > Terry, do you

Is it time to discuss Leo in a MacInTouch lovefest for Dave Winer's MORE outliner?

I recall reading that MORE was one of Edward's inspirations for Leo. A MacInTouch discussion of reminiscences of old technology is full of praise for MORE's technology, starting with this comment . -- You received

Re: I love Leo, but... Scrivener and Org-Mode

On Saturday, March 3, 2018 at 7:50:31 AM UTC-5, Israel Hands wrote: > > What do I use Leo for then? > > Content - for me content is king. Manipulate it - tag it - filter it - > anything you like but it's about content. > > So my first use of Leo is as a free form database for notes, minutes, >

Re: Rethinking Leo's distribution process

On Saturday, March 3, 2018 at 9:06:12 AM UTC-5, Edward K. Ream wrote: > > > ​I would happily abandon all the work we have done, except perhaps > assoc.exe. > Unless I misread the current situation, the NSIS installer for Leo and all its files is no longer in use - the file association is all

Re: I love Leo, but... Scrivener and Org-Mode

On Saturday, March 3, 2018 at 8:16:33 AM UTC-5, Edward K. Ream wrote: > ​#774 Convert Leo trees to LaTex as in Scrivener > is a new > enhancement request. > > Googling "scrivener convert to LaTeX" yields this page >

Re: The first, urgent task: show people what Leo already has

On Friday, March 2, 2018 at 11:27:59 AM UTC-5, Edward K. Ream wrote: *2. Better support for markdown* > > #767: Add markdown command similar to rst3 command > . I want to move > Leo's docs to markdown. > > #763: Use html comments to support

Re: How did I came across Leo?

On Saturday, March 3, 2018 at 7:56:48 AM UTC-5, Edward K. Ream wrote: > > On Sat, Mar 3, 2018 at 6:49 AM, David Szent-Györgyi <das...@gmail.com > > wrote: > > ​> ​ > My coworker's motto was, "If it's stupid, and it works, it isn't stupid"! > > ​Hehe. It

Re: Rethinking Leo's distribution process

A decade ago, when you were kindly using NSIS to generate proper Windows installers for each release of Leo, I worked on an enhanced NSIS installer. In those days, it was possible to install Python itself for all users of a machine or for the current user only, and I figured out how to handle

Re: Rethinking Leo's distribution process

On Thursday, March 1, 2018 at 12:49:48 PM UTC-5, Edward K. Ream wrote: > > On Thu, Mar 1, 2018 at 11:11 AM, Matt Wilkie > wrote: > >> >> - No need for sourceforge, pyinstaller, windows installer. >>> >> >> The only significant advantage of those installers over the pip install

Re: How did I came across Leo?

On Saturday, March 3, 2018 at 2:39:59 AM UTC-5, Edward K. Ream wrote: > > On Fri, Mar 2, 2018 at 11:39 PM, David Szent-Györgyi <das...@gmail.com > > wrote: > >> I employed Leo for an oddball use case, which it addressed beautifully. >> > > ​ > Quite an

Re: How did I came across Leo?

I employed Leo for an oddball use case, which it addressed beautifully. How long ago did this start, perhaps 2005? The job that I held then required that, without help from work infrastructure or from colleagues, I write tools for diagnosing and repairing problems with installations of a

Electron documentation on best practices for security

To my knowledge, none of us earn a living working on Leo and related projects, which means leveraging pre-existing code saves one the effort of reimplementing that. Electron may prove to be immensely useful for Leo and related projects such as a desktop application made from LeoVue. Since I

Re: Distribute only 64-bit executables?

On Monday, February 5, 2018 at 12:22:30 PM UTC-5, Edward K. Ream wrote: > > I am thinking of installing only 64-bit software on my Windows machine, > and to release only 64-bit pyinstaller builds. Here are my thoughts: > > 1. Every distribution option doubles the amount of testing required for a

Re: #561: Please explain why making Leo a jupyter client is important

On Sunday, October 29, 2017 at 6:02:35 PM UTC-4, Offray Vladimir Luna Cárdenas wrote: > > Collaboration could be done as a desktop app with the proper support for > Jupyter kernels with ZeroMQ. As for the Python/Web/Javascript > integration, Dash seems pretty interesting and Flask is a minimal

Licensing concerns raised by new terms of service for GitHub

I don't know that this is an issue, but a change of terms associated with an essential service need to be checked with care. According a blog entry posted on March 1 by Debian Developer Joey Hess, The new TOS is potentially very bad for copylefted Free Software. It > potentially neuters it

Re: Why is Leo great?

On Friday, July 8, 2016 at 10:26:45 AM UTC-4, Karsten Wolf wrote: > > > > On Tuesday, July 5, 2016 at 7:46:21 PM UTC+2, Propadovic Nenad wrote: > ... > >> I'd appreciate examples which *show* me why Leo is great. I really want >> to love it, honestly. I *tried* to find it extremely useful ten

Re: Leo 5.1.1 final coming March 4

On Thursday, February 25, 2016 at 7:38:36 AM UTC-5, Edward K. Ream wrote: > > I recently had an Aha about releases: minor bugs don't matter! Leo's > latest code is typically more stable than any previous "final" release, so > we should release "final" releases much more often. Say every two

Re: Leo 5.1.1 final coming March 4

I tried the experimental PyInstaller set-up you released a few months back, under 64-bit Windows 7. I have not used it, because it uses Python 2.7.8, which is no longer supported and contains known security holes that have been patched in subsequent updates. Would it be possible to check all

Re: Revisiting the generation of the .nsi install script

On Sep 7, 7:05 am, Edward K. Ream edream...@gmail.com wrote: I sympathize with the goal of making it easier to change the installer script. I don't usually like to do that by creating three external files that must be kept in synch :-) It's already bad enough that we must remember to bzr

Re: Revisiting the generation of the .nsi install script

On Sep 7, 9:01 am, Edward K. Ream edream...@gmail.com wrote: On Mon, Sep 7, 2009 at 7:47 AM, David Szent-Györgyi das...@gmail.comwrote: Your proposal -- putting all the boilerplate in a .txt file  -- would allow me to maintain all the code in one place. It would still mean editing

Revisiting the generation of the .nsi install script

Bear with me in this long essay. I have to convince Edward to abandon code that he has just written. I do have a replacement in mind, which I describe. I also have a Leo story to tell -- one that shows that my experience using Leo has soured me on working without it! With a new scheme for

Re: What to do about the windows installer?

On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file.  I don't know whether this hack

Re: What to do about the windows installer?

Google Groups hiccuped, and may have devoured my reply. Just in case, I am re-writing it. On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth.  I also know

Re: What to do about the windows installer?

On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth.  I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about