Re: OT: American Scientist: Expanding Consciousness

Fascinating! Saving for a re-read over the weekend when I can reflect on it more completely. -- 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: Leo 6.1 final released

> > Do you mean that TravisCI published the release automagically? Or, as I > suspect, did one of your scripts do that? > Yes, Travis is set to automatically publish tagged releases on master branch -- provided a) the tests in `run_travis_unit_tests.py` pass, and b) a local inside-Travis

Re: Leo 6.1 final released

> Full details are here > , on GitHub. > > I would like to wait a day before telling the world. There were a few > last-minute glitches. > Happily https://pypi.org/project/leo v6.1 seems to have been published without a hitch.

Re: Guide to writing better software documentation

> > ... to break Tutorials into "for the committed" and "for the curious". In > the latter, experienced Leo people could be encouraged to write simple > examples of "How this Leo feature helps me to accomplish the things I > actually use a computer for." > I like this formulation,

Re: How is Leo's website published?

> How is Leo's website published? >> > > I use FileZilla to upload files to a site > provided by hostgator.com . > Oh, so you select certain directories and files and push them out? That explains why I couldn't find a script! ;-)

How is Leo's website published?

How is Leo's website published? I'm most interested in the "upload {...} to server" part, but others like Gar and Rob are probably interested in the general workflow. My context: some of the files in the root of a source code checkout are on the website, http://leoeditor.com/load-leo.html for

pushing setup.py changes to devel

Edward, a heads up that I'm about to push some changes to devel branch. All in `setup.py` so impact is minimal. -matt -- 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

Re: I was sick as hell :(

> > Had the flu, bed ridden and incapacitated for days, I'm feeling better now > :) > Welcome back! Don't push too hard; keep the sleep up. I didn't do that last go 'round and went back down for a couple extra days. -- You received this message because you are subscribed to the Google

Re: Guide to writing better software documentation

I agree Tutorial and How-To division could overlap in some contexts. The takeaway for me was separating Explanation and Reference from both. I've watched many of my guides get tangled up and end up more confusing when I mix 'splaining and recipe-ing in particular. I'm happy to have new lenses

Re: Leo 6.1-b1 released

> > (Leo-6.1-b1) PS C:\Users\Viktor\pyve\Leo-6.1-b1> > leo-c > ... > can not import _curses. > Windows: pip install windows-curses > Yup, that's a bug. Please open an issue on Github so I don't forget about it. (Full log not

Re: Trying to install Leo

thank you for the follow up report Reinhard. I'm glad something worked! Under Settings menu there is a new item called "Desktop Integration". It contains scripts which will create Menu and Desktop shortcuts to launch Leo with a single click. They're not *quite* ready for widespread use, but

Re: Leo [6.0-final & 6.1-devel] have a problem with user-/ session-specific cache

that does sound strange. What happens if you open ".leo/myLeosettings.leo" using "File >> Open-outline" instead of opening "Open specific Leo file"? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Trying to install Leo

> I've been using Leo for more than 20 years so I know its value. Anyone > else is going to have the reaction of the guy who wrote the negative note > on Sourceforge. It is not reasonable to expect anyone to install this > software unless they already know the software and are determined to

actual required version of PyQt

Edward, Vitalijie, What is the actual required version of PyQt? I've been taking the lazy path in setup.py and saying "just use whatever is current", however as Reinhard recently reported that means we're now incompatible with Anaconda's out of the box Spyder: ERROR: spyder 3.3.6 has

Re: Trying to install Leo

Thanks Reinhard. I've not tested on full Anaconda and from your report that shows. You're installing from the (base) environment, which means anything you do in it is not isolated from the other possible python environments and apparently Leo and Spyder (which Anaconda ships with) ask for

Re: A small pause for a better fstringify

Thank you :) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit

Re: Trying to install Leo

> Just got a new Mac and was unable to install Leo after 2 hours of trying. Oh that's ugly. Ouch. The most recent Mac install debugging effort has been here: https://github.com/leo-editor/leo-editor/issues/1288. I think the successful install path will resemble: - install Anaconda (via

Re: A small pause for a better fstringify

> I am ever more convinced that using tokens is superior to parse trees for > text munging. > Text munging I understand, but not parse trees and tokens. Can you give a one or two sentence overview? -- You received this message because you are subscribed to the Google Groups "leo-editor"

Guide to writing better software documentation

Found by way of Guido von Rossum in python discussion forum: https://www.divio.com/blog/documentation/ Basically: recognize there are 4 kinds of documentation, serving different functions. Design, write and store them differently. It's in mixing them up in one document/place that leads to mess

Re: 6.1 coming soon. Devs, please hold commits to devel

Will do. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit

Re: "Summary of ..." issue items as wiki pages?

> > Issues and labels cost nothing. They are the "secret" to effective work > flow and project management. > After reflection I realize this is really about how many clicks it takes me to get to my preferred issues views. If I rely only on Github's default presentation (click on [Issues] tab)

"Summary of ..." issue items as wiki pages?

Issues like "Summary of Info items" gives me a a kind of jarring feeling. They can never be closed if we want them easily found, and, for me anyway, there's a strong ever present subtle tension to fix and close everything possible. Perhaps items like these would be better served as wiki pages?

Re: ENB: Time travel, space filling curves, I Love Lucy etc.

Riffing on topic of Lucille Ball: in addition to the iconic *I Love Lucy* she was responsible for *Star Trek* and *Mission: Impossible*, among others. I couldn't find the the revolving

Re: docs: Installing Leo from sources (all platforms)

> > I leave the technical details for Matt to explain - but - we now finally > reached a state, where the underlying issue is clearly identified :-) > https://github.com/leo-editor/leo-editor/issues/1415 - Leo crashes on startup with unexpected exception loading session and then unexpected

Re: docs: Installing Leo from sources (all platforms)

> > I can demonstrate, that such an installation works, if the "Leo-devel" >> instance starts w/o an existing '~/.leo' directory - and - on the other >> hand consistently fails, when my existing '~/.leo' directory is used. >> > > Well done, Viktor. Thanks for your persistence. > Viktor's

Re: Markdown preferences

I use markdown most of the time, because I've learned it, and that largely due to the amount of time spent in the Stack Exchange network and now GitHub. However I increasingly chafe under markdown's limitations and have targetted as Asciidoc as my escape path. I tried rst but balked at the

Re: For Leo 6.0 on Windows 10 - PyQt 4 or PyQt 5?

> > Work around: > > set HOME=%USERPROFILE% > mkdir %HOME%\.leo > echo "My ID" > %HOME%\.leo\.leoID.txt > leo-console > > Note: skip the `set HOME` line if you already have it defined. > *DON'T* quote My ID or you'll break your .leo files. See

Re: Understanding a large code base?

Edward will likely chime in soon, but an intermediate method is enable the *active_path *plugin. After restarting Leo, create and select a node with "@path some/place" and see 'Plugins >> Active path' menu. Recognized file types will open with @auto or @asis when double-clicked. (@clean is

Re: get path of running script?

> > What's Leo's idiomatic way to get the path of the currently running script >> in Leo? >> > > Not sure I know what you mean by the "currently running script". There > are several ways of getting important directories. > I meant the name of the file that is created and then run when

Re: get path of running script?

c.writeScriptFile seems to be where it is created. I haven't found a place yet for retrieving it; maybe it's too shortlived to bother with. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

get path of running script?

What's Leo's idiomatic way to get the path of the currently running script in Leo? I've been using the below, but it's proven unreliable in Leo (differs between `Ctrl-B` and `--script=xx`), and there's probably already a Leo function which does this anyway, right? def get_my_path():

Re: docs: Installing Leo from sources (all platforms)

> Please take this discussion offline, and summarize your results on > leo-editor when you have resolved this. > Yeah, this is pretty noisy. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: interesting places on the web

> I don't follow this discussion for clickbait. Explain why this site is > relevant to LEO, please. Thank you. It's not about Leo. I tried to pick a subject line that made that clear but I guess that didn't work. From time to time I share things that I discover "out there" that are

Re: docs: Installing Leo from sources (all platforms)

Viktor does this work? (adjust to wherever launchLeo.py is): python C:\Users\Viktor\pyve\github\leo-devel\launchLeo.py > Pfad nicht finden: > 'C:/users/viktor/pyve/ve4ileo/lib/site-packages/leo/doc/quickstart.leo' > [...] > (leo-devel) PS

Re: Matt: OK to release Leo 6.1 b1 this Friday?

I don't see anything of mine that should delay a release. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this

interesting places on the web

Every once in a long while I run into a site out there in digital space that renderes me speechless and I just can't stop exploring and reading and clicking. Sometimes it's the eye candy, other times it's deep thoughts, or cool new user interface paradigms, or just damn interesting people. And

Re: docs: Installing Leo from sources (all platforms)

> > PS C:\Users\Viktor\pyve\github\leo-devel> pip install --editable ./devel > > ERROR: File "setup.py" not found. Directory cannot be installed in > editable mode: C:\Users\Viktor\pyve\github\leo-devel\devel > 1 dir too deep. The path needs to

Re: docs: Installing Leo from sources (all platforms)

> > Direct ``pip install >> https://github.com/leo-editor/leo-editor/archive/devel.zip`` >> does *not* >> work. For proper operation Leo relies on presence of certain files outside >> of the standard Python `site-packages` folder

Re: How do you install leointeg into VS Code?

> > Maybe with Anaconda we need to use a different way to properly invoke the > environment? > I forgot the details of why, but for my cmd shell I use this: > > %windir%\System32\cmd.exe "/K" C:\Programs\Anaconda3\Scripts\activate.bat > This will invoke conda's root or base environment but

Re: For Leo 6.0 on Windows 10 - PyQt 4 or PyQt 5?

> > Also, I want to run leo headless: so I wonder if theres a way to set the >> 'leo id' without qt. (on first run leo asks for an id ) >> > > Try running `leo-console` (or `python launchLeo.py --gui=console`). > [Later]: doesn't work. Loads npyscreen and then exits. This is probably a >

Re: For Leo 6.0 on Windows 10 - PyQt 4 or PyQt 5?

> > I am currently trying to install leo on windows... (I wish the > documentation would be a lot more detailled and precise for this) > Yeah, I hear you. After installing python3 with the official installer, It took me a lot of > googling to figure out that I needed to put python3's path

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

> > I think I'm just going to declare the incantation of `pip install >> http://path/to/leo/archive.zip` as >> broken beyond reasonable repair and that people have to use either PyPi or >> git clone (when using pip). >> > > Looks like I'll have to bite the

Re: Improved asciidoc, asciidoctor and pandoc support

> > > For me the external file is not created. See the desktop-integration.leo >> file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. >> > > Matt, what's the status of this now? > It works after installing asiidoc3. I didn't understand that @adoc is fundamentally different from

docs: Installing Leo from sources (all platforms)

I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

> > Following a similar recipe using Conda I confirm `global config dir: None` >>> and `No @menu setting found` log window messages. I also have critical >>> missing folders in "PYTHONHOME\Lib\site-packages\leo", like Icons. Digging >>> in... >>> >> >> Can you give already a status update on

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

> Following a similar recipe using Conda I confirm `global config dir: None` >> and `No @menu setting found` log window messages. I also have critical >> missing folders in "PYTHONHOME\Lib\site-packages\leo", like Icons. Digging >> in... >> > > Can you give already a status update on any

wanted: new user first run screenshots of Leo

Follow up from https://github.com/leo-editor/leo-editor/issues/1190#issuecomment-540007245. Please pretend you are a new user (or maybe you actually are!) and post a screenshot of what Leo's first ever load looks like on your system to this thread. Recipe: *set home to an empty folder or move

Re: Installing AsciiDoc on windows

> > Thanks for this. Still, I think the slight extra difficulty in installing > asciidoctor is well worthwhile. > :-) Asciidoctor install recipe: choco install ruby refreshenv gem install asciidoctor asciidoctor --version *choco*latey : it's apt-get/yum/pip

Re: Installing AsciiDoc on windows

I added a version of this to LeoDoc.leo at 10171e16afa22f2e07b9651f9c2819a0e964dfd7. Feel free to rework or even remove. -matt -- 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,

Installing AsciiDoc on windows

The new Leo @adoc directive and the adoc command need either Asciidoc3 or Asciidoctor tool installed and in PATH. Asciidoctor is probably the best of the two to use, but installing on Windows is not straightforward as one needs to install Ruby first. Asciidoc3 isn't the straightest either, but

Re: The leo/plugins folder no longer contains pyzo's sources!

> I recently discovered the marvelous *find_executable *function in >> python's distutils.spawn module. This function has changed how I think >> about inter-process communication. >> > > Thank you!! > This prompted some research on how to use the function, which turned up this alternate

Re: The leo/plugins folder no longer contains pyzo's sources!

> > I recently discovered the marvelous *find_executable *function in > python's distutils.spawn module. This function has changed how I think > about inter-process communication. > Thank you!! -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: Where is the demote command? Why does the tutorial not link to it? Why is it not in the Outline menu?

Plus, making sure it's not overlooked, you can move nodes around with keyboard shift-arrow as well as with the commands. For me thus is usually more convenient. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: Improved asciidoc, asciidoctor and pandoc support

> > Please report your experiences with these new features. > For me the external file is not created. See the desktop-integration.leo file at rev f0c07886d25ea892b15159d00f4ef531aae8a723 in devel. Leo Log Window Leo 6.1-devel, devel branch, build bd1ac64b20 2019-10-07 10:51:57 -0500 Python

Re: Success! Sant Mat lineage chart converted from Freeplane to OPML to Leo to LeoVue!

Great to hear of success from outside the usual suspects developer pool! > Leo was rendered on the web via LeoVue: > http://santmat.livingcosmos.org/surat-shabd-yoga/ssy-leo.html#/t/1 > Unfortunately I get the table of contents on the left but the body pane remains blank. Using the collapsed

Re: leo from devel fail to start on windows

This happens to me from time to time as well. I haven't figured out what precipitates it. So far `pip uninstall leo && pip install --editable path\to\leo-code` has fixed it. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Usage of "Leo-devel" archives from GitHub installed via pip into a dedicated PyVE does not work

Following a similar recipe using Conda I confirm `global config dir: None` and `No @menu setting found` log window messages. I also have critical missing folders in "PYTHONHOME\Lib\site-packages\leo", like Icons. Digging in... -- You received this message because you are subscribed to the

Re: Leo coming soon. Question for Matt.

Sorry, I can't see. The log files seem to have been stripped from https://groups.google.com/d/msg/leo-editor/lshKKfYbILM/546TIe5KBgAJ > *Should it be possible to upgrade Leo in a given Python Virtual > Environment from one Git revision to another one using the command "pip > install

Re: Devs, please don't add commit_timestamp.json

I've removed my git hooks, but I use several computers and may have missed one. I'll take another look. -- 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: leo 6.1 user expirience issues

Is there a way to save and then share layouts? (across .leo files, across people) -- 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: Issue #1341, security issues with path expressions

> > #1338 fixed a > serious bug that could lead to the unexpected execution of code. > g.computeFileUrl was expanding path expressions of the form {{text}} within > arbitrary body text! > Eeep! Good catch. I'm glad you noticed it. -matt

Re: leo 6.1 user expirience issues

> since leo 6.1 is not released yet and there's a time to make changes I > want to report some problems > first of all I discovered some huge ui problems: > Gar makes an important point. The first experience of the new docks ui is startling and somewhat alarming, especially for people who

Re: where are the a="xxx" in leo files?

> > It makes sense : marked nodes, along with the currently selected node as > the file was saved, are now a 'personal' thing only visible to oneself as > they work on a project. makes sense. > There is also `@bool put-expansion-bits-in-leo-files = True` which saves the tree open/closed

Re: blacken-tree now blackens all of Leo's core without apparent problems

To make sure I catch the drift as I haven't been following closely: the Beautify commands will create the same results as Black (excepting overindented comments), but is using it's own code to get there? and is markedly faster? So it's really Black Beauty? In that case, once the dust

Re: where are the a="xxx" in leo files?

Do you mean "userAttributes" a.k.a. "unknownAttributes"? https://leoeditor.com/customizing.html#ua-s-extensible-attribues-of-nodes (Just guessing. I don't know anything about the leo file format.) -matt -- You received this message because you are subscribed to the Google Groups "leo-editor"

Re: Chris: cause of outline artifact?

> > With all else being equal (this took some effort), if the python > environment leois running under is native to the OS the stylesheet is > flawless. If leo is running under a venv of any flavor (including conda) > the artifacts appear. > Sounds like time to reach out to a wider community,

Re: Second thoughts about f-strings

Thank you for reporting on the variety in the to-be or not-to-be f-string landscape. This side by side comparison useful. -- 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

Re: I have just protected the devel branch

Good idea. I didn't know that was possible. Going to do the same on some of my own. -matt -- 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: Present plans

> I hope you all will remain patient with me. Nobody is as eager to finish > all these nifty projects as I am. > You have mine.This part is easy for me. I simply can't do what you can do! ;-) -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: Discusss: use Discourse instead of mailing list

> The biggest downside to email lists is formatting the messages. Plain text > is good, but code, images, proper indentation etc. is better. > The major reason I shifted participating primarily via browser in this list. Flarum vs Discourse vs Nim Forum: at the moment I side with Discourse,

Re: Discusss: use Discourse instead of mailing list

Chris George wrote: > > So I broke my leg this morning. > eeep! Sorry to hear that. Eat a a couple cans of salmon/tuna a week, bones and all (adice via a friend with broken arm, via his doc), helps with bone fusing/regrowth. My wife took something called "osteo pro" when her broken shoulder

Re: Discusss: use Discourse instead of mailing list

> > Reply-by-email enabled for all Discourse customers > > > Thanks for the correction. I appreciate it. -- You received this

Re: Studying Robert Cholette's vs-code leointeg project

> > It would be really cool to animate the gitk commits, showing (in Leo) what > each commit did. Leo git-diff command and other git utils provides the > basis for such an "animation". I'm tempted... > I remember Vitalije did something like this using Fossil, Rust and Leo:

Re: Discusss: use Discourse instead of mailing list

> > every time anybody switches from email to some closed, web-based service, >> membership & traffic drops off tremendously (even with email >> notifications). People continue to use email lists because they work. >> Nothing works as well as a good email list, with a searchable archive. My

Re: Why I want to blacken most of Leo's sources

I'm happy to have black available and used by default. I know all of my own stuff could use it. I tend to constantly switch between single and double quotes without much rhyme and reason, so normalizing would be good. Somewhat related is *isort* - https://github.com/timothycrosley/isort, for

Re: The leo_in_pyzo plugin is ready for testing!

> > The pyzo_in_leo.py plugin requires --global-docks and the qt gui, which is > Leo's default. It is incompatible with --no-dock. > git checkout devel git pull leo # add pyzo_in_leo.py to @enabled-plugins node in myLeoSettings.leo # save, exit leo --global-docks On load the Outline panel is

Re: The leo_in_pyzo plugin is ready for testing!

> > It helps a lot. Please remind me what platform you are using. >> > > Leo 6.1-devel, devel branch, build 05e1e94daf > 2019-08-28 02:48:56 -0500 > Python 3.6.8, PyQt version 5.12.3 > linux > I think he meant also which linux distribution. -matt -- You received this message because you are

Re: Discusss: use Discourse instead of mailing list

> > (b) The Google Group has a lot of history and is a major resource when >> answering questions. I wouldn't want to talk about things in one place and >> research in another. There is conflicting info on whether the free hosting >> supports imports (I've asked >>

Discusss: use Discourse instead of mailing list

in https://groups.google.com/d/msg/leo-editor/oQwOLKtiAlg/XfKuuBhUBgAJ Xavier recommended using Discourse instead of Google Groups for Leo discussion: * I think it would really great for our community if we moved our > discussions to a real modern forum like Discourse >

Re: I've just killed two issues

Whoa. Edward, the strength of your reaction seems out of proportion. matt -- 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

Chris: cause of outline artifact?

Hi Chris, i saw this in passing and wonder if it might be the same thing you've been running into with the theme weird outline in outline thing. "*11) Set outline: none; when styling inputs and buttons* or they will get an outline like the below when clicked/interacted with:

Re: #1289 (Global docks) is ready for testing

On open I see a Leo window with several internal panels like I'm used to (Outline, Body, Tabs, Render) and 4 new brightly coloured panels (Test1, Test2,...). The 4 test panels can be snapped off the main Leo window using min/max icon at top right by [x] and float independently anywhere on my

Re: best practice for managing calendar events

Have a look at todo.py plugin. I think it's enabled by default, see [Task] tab next to [Nav], [Tags] etc. (Disclaimer I haven't used it) matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: I've just killed two issues

> > Hang on, I've just described a cache. I don't think that is what you're > pointing towards, because that wouldn't make finding and changing the > setting currently of interest any easier. > Oh but it could! If each cached setting had a breadcrumb trail back to where it was set. -- You

Re: I've just killed two issues

> > After editing settings in the myLeoSettings.leo or any other settings > outline, user should invoke a command to save settings. This command can be > executed automatically on each save. This command would read settings from > the outline and build settings dict as it is now done during

Re: I've just killed two issues

Clearly you've devoted some concentrated thought to the challenge Vitalije. I love the idea of setting levels 0,1,2,... and the setting being able to report on it's level. Is there anything a person of small dev skills like myself can do to help prove/isprove the approach is sound and

Re: I've just killed two issues

It's too bad there's no obvious path forward. Maybe one will present itself eventually as we dwell here longer. Good that increased complication without clear gain has been avoided though! -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: New Themes

> > After using venv, pyenv, and conda and having them all display the same > problems I can pretty much say that it has nothing to do with the pyqt > version and everything to do with virtual python environments. > > When you did your testing were you using a virtual environment? If so, >

Re: New Themes

> > >>- Default font size much too large, everything is pretty squished. In >>screenshot below compare the window manager title with Leo's tab title. >> >> I dropped it by 1px across the board and could probably go smaller. At > 1920x1080 my eyes just aren't that good anymore. :-) > I

Re: New Themes

> > Blue sky: I'd like to be able to run `show-settings` into a Leo panel, > that has a filter category buttons plus a text field at top. From there I > could 2x-click or [enter] on any given setting and be taken to the location > where that is currently defined (LeoSettings, myLeoSettings, >

Re: New Themes

> > I have always thought it rather puzzling to have self-contained themes and > then an entirely different way to set fonts. > My preference is to set everything related to UI in the theme. > I agree, all UI elements should be in one place. However people shouldn't have to wade through tons

Re: ENB: re singleton docks

> > I am considering switching to g.app.db for sizing Leo. That is, Leo's > main window would open with the size it happened when it last closed, > *regardless* of what outlines are being opened. Imo, this would be more > intuitive for users. This would also remove some

Re: New Themes

A structural problem: theme font-size overrides myLeoSettings.leo, which I assume applies for all settings. I expect myLeoSettings to always have the last say. Oh that's interesting, the `show-settings` command does not report base font settings, e.g. @font-size, @medium-font-size, etc.

Re: New Themes

> > Thank you for tackling and sharing this Chris. Feedback to come when I > finish catching up on the last month or so of activity that I've been apart > from. A lot has happened! > Well I'm not caught up, but have started exploring the themes anyway ;-) *ZephyrDark* on Linux Mint 18 laptop,

Re: How to customize look?

> > Suggest to put this procedure in the document something like a best > practice(for newbie?).. > Recorded at https://github.com/leo-editor/leo-editor/issues/1191 -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: Fman Build System licensing

*Edited conversation with Micheal Hermann:* - From: Matt Wilkie Hi, A colleague pointed me to the Fman Build System as a solution for many of our packaging and distribution problems. However the licensing description at https://build-system.fman.io/ sounds problematic. Our project

Fman Build System licensing

from "Re: Linux Snapcraft and Packager integrations are broken " thread: We might not be allowed to use FBS because of licensing: *"To comply with > its license, you need to open source your application itself under the GPL,

Fman Build System licensing (was Re: Linux Snapcraft and Packager integrations are broken)

We might not be allowed to use FBS because of licensing: *"To comply with > its license, you need to open source your application itself under the GPL, > or buy a commercial PyQt license"*. This is probably because they solve > some of the packaging and distribution problems by bundling PyQt,

Re: Linux Snapcraft and Packager integrations are broken

We might not be allowed to use FBS because of licensing: *"To comply with its license, you need to open source your application itself under the GPL, or buy a commercial PyQt license"*. This is probably because they solve some of the packaging and distribution problems by bundling PyQt, which

Re: Linux Snapcraft and Packager integrations are broken

Interesting! Better link: https://build-system.fman.io/ I might be able to help with setting up a dedicated Windows machine for builds if vbox doesn't work. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group

<    1   2   3   4   5   6   7   8   9   10   >