Re: On the Semantics of Copying Clones

On Saturday, May 23, 2020 at 7:02:46 AM UTC-3, Edward K. Ream wrote: > > > Thanks for this excellent clarification. This should be doable with a a > new command, say, paste-retaining-only-clones. I have just created #1593 > for this. > >

Re: Leo for organizing notes?

Hi Andy, I've not made any comment till now because I'm really short on time, but I have to say that I find this thread REALLY fascinating and a source of really good and stimulating ideas! So I would greatly appreciate if you go on with all this conversation in the open, either if it's here or

Re: Discusss: use Discourse instead of mailing list

> Discourse and similar tools are doing the same for communication and > community building. > I have just read https://www.discourse.org/testimonials and here are some of the quotes that resonated the most with my own feelings about Discourse: *“It’s really oriented towards community* and

Re: Discusss: use Discourse instead of mailing list

> > Actually, I am thinking that we should just stick with Leo's existing > forum and issue tracker. I don't see any major benefits to changing how we > communicate. > > Edward > Jeje, it's weird to hear that from the author of a piece of software that *is* changing the way we work with code

Re: Discusss: use Discourse instead of mailing list

On Saturday, August 31, 2019 at 7:44:34 PM UTC-3, Chris George wrote: > > So I broke my leg this morning. > > Ups! I hope it's not serious and you get well soon! > Since I will have a fair bit of downtime coming up I would be happy to > work on the import/backup to see what can be done. >

Re: Discusss: use Discourse instead of mailing list

On Friday, August 30, 2019 at 11:11:48 AM UTC-3, Chris George wrote: > > I am currently looking at Flarum which seems to be a better fit than > Discourse. More eyes and thoughts would be good. > > Sign in and I will make you an admin if you want to evaluate it. > > I didn't know Flarum and I

Re: Discusss: use Discourse instead of mailing list

On Friday, August 30, 2019 at 11:02:29 AM UTC-3, Edward K. Ream wrote: > > I tried and failed to sign up for discourse. There is an email fallback. > > Has anyone tried to register before? If not, I'll register via email. > > I successfully registered using the same Google account I use for

Re: Discusss: use Discourse instead of mailing list

> People continue to use email lists because they work. Nothing works as >>> well as a good email list, with a searchable archive. My advice: Don't. >>> Just don't. >>> >>> Thanks for this advice. Any comments? >> > > Mile's observation is valid and real. > I'm afraid it is not in this

Re: Discusss: use Discourse instead of mailing list

Thanks Matt for creating this topic about my proposal! I've just seen that they have just answered to your question . Regarding the things they take into account to consider a community as a valid "candidate", at the

Re: I've just killed two issues

> Let's let newbies speak for themselves. > I think it's time to speak! Regarding the Leo settings "world": for a Leo newbie like me, settings in Leo are a complicated issue for sure. So it's something I try to avoid touching as much as I can... but just because the UX is really poor. Some

Re: Two birthday stories on my 70th birthday

Happy birthday Edward! It's being a pleasure being a part, though little, of your life and walking this path with you. The love and enthusiasm in Leo *are first of all yours*, and this profoundly shapes the enriching atmosphere of the whole Leo team. Thanks for being who you are! I'm

Re: Answering my inner critic

Edward, you did nothing wrong in your first post. There is no "mistake". Maybe your initial idea for the post was that one, but you ended up expressing the hope that it may help others (it uses to happen to *natural teachers* as you are): I hope this post helps others ignore their inner critic

Re: Answering my inner critic

Thanks Chris. That's it! Oh, and for those that do still believe in the tale that brain power or your IQ is the *determining factor*, here's the "scientific proof" from someone that studied it deeply until she found the truth: Grit: the power of passion and perseverance

Re: Answering my inner critic

On Sunday, April 21, 2019 at 11:34:45 PM UTC-3, Xavier G. Domingo (xgid) wrote: > > Thanks for sharing this, Edward. The truth that I discovered in recent > years and that helps me handle the inner (negative) critic goes something > like this: > > Wisdom is only gained

Re: Answering my inner critic

Thanks for sharing this, Edward. The truth that I discovered in recent years and that helps me handle the inner (negative) critic goes something like this: Wisdom is only gained through experience. And the experience that teaches you more is the one that beats you harder. That is, the one that

Re: Leo in 2019

On Wednesday, April 17, 2019 at 10:40:19 PM UTC-3, Joe Orr wrote: > > > Also realized I need to add tag buttons (like in Jira), probably can knock > that out soon. > > [tag 1] [tag 2] > > click on tag button filters for that tag. > Great Joe! That would fullfill yet another of my most awaited

Re: Leo in 2019

On Saturday, April 13, 2019 at 12:41:50 PM UTC-3, Joe Orr wrote: > > > 1. There is a lot of noise. For example, the placement of a node and the > length and shape of a string has no meaning. In a tree interface child > items form a list. > 2. There isn't any way to treat the nodes as data,

Re: Who should be using Leo

El 20/01/2019 a las 1:41, rengel escribió: I'm not an evangelist for TheBrain, but just tried to point to a tool that might be useful to others... And I thank you for that, Reinhard! I didn't know TheBrain until you mentioned and I like some of its features. My contribution did not pretend

Re: Who should be using Leo

I'm a programmer, but are not yet using powerful scripts (although it's on my plans), so I don't qualify for the first reason yet. I do qualify for the second, but I would add two other KILLER FEATURES that make Leo beat others IMHO: * Re-organizing your nodes is a snap! I can change what

Re: Problems trying to run LeoWapp

Great! After switching to the latest skeleton commit from this morning (Commit hash: 324649a689927aee0b847bf7a16f2d7285c53aed), it's working for me with the usual: python launchLeo.py --gui=browser Now playing with the new GUI. I like it!! On Thursday, December 6, 2018 at 6:58:18 AM UTC-3,

Problems trying to run LeoWapp

Today I've updated Leo to the latest current devel version in GitHub: Leo 5.8.1 devel, build 20181204214531, Tue Dec 4 21:45:31 PST 2018 Git repo info: branch = devel, commit = 09f59c3537f8 Python 3.6.2, PyQt version 5.6.2 Windows 10 AMD64 (build 10.0.17134) SP0 ... and then tried to run the

Re: How important is LeoWapp to you?

For me LeoWapp is a total game changer! As I mentioned in the past, some of the important missing points I find in Leo are easier access to node's additional data (like tags, attribs or links) and a more integrated (co-located) visualization of this data. I tried in the past learning the Leo

Re: The LeoWapp prototype has succeeded!

Let me be the first to give you my most sincere congratulations!! You've made an excellent work in this project and it opens new and really exciting opportunities for the future of Leo and the interactive data and PIM worlds alltogether! Some serious health issues have prevented me from being

Re: Three demos showing how to improve drawing speed

On Friday, July 13, 2018 at 4:14:53 PM UTC-3, vitalije wrote: > > Me too. It seems after all we still have a healthy open source community. > Let's keep it that way. > Vitalije > I'm also really glad to hear this! I'm sorry I have not been able to say any encouraging word before nor to be of

Re: tree icons

On Thursday, March 22, 2018 at 12:21:08 PM UTC-3, Terry Brown wrote: > > Yep, now I've worked with it a bit more it's definitely not finding the > same icons, and using light versions of icons used by the todo plugin > for example. So really it just looked somewhat better because it was >

Re: OT: A better way to code, by Mike Bostock

8:53 AM UTC-3, Terry Brown wrote: > > On Sun, 18 Mar 2018 01:15:04 -0700 (PDT) > "Xavier G. Domingo (xgid)" <xgdo...@gmail.com > wrote: > > https://github.com/leo-editor/snippets/blob/master/utils/pytest_switch.py > > is an example of how Leo can help br

Re: Please consider becoming a Leo dev, even if you aren't a programmer

> > But doing something about the ugly bits is typically difficult or >> impossible. For starters, I recommend the easy things on the to-do list. >> They are typically marked with the First label >>

Re: OT: A better way to code, by Mike Bostock

Great! Many thanks for your encouraging words. So I think I should try to explain first what I mean by "talking code". The idea is simple: when someone tells you that he is a programmer, he's telling you what he DOES. But that's not, by far, all he IS. There's much more he can *tell* you

Re: Please consider becoming a Leo dev, even if you aren't a programmer

OK, thanks for your comments. I'll take a look and see what get's my attention and let you know. On Saturday, March 17, 2018 at 6:54:58 AM UTC-3, Edward K. Ream wrote: > > > > On Sat, Mar 17, 2018 at 12:15 AM, Xavier G. Domingo (xgid) < > xgdo...@gmail.com >

Re: OT: A better way to code, by Mike Bostock

I have to admit that we are on the same boat here! After 30 years of programming, with 20+ programming languages including rare gems like CLIPPER and CHILL, I knew I was at home when I found Python. And I'm not going to change this, at least on this life! But I know that we *can get the goal

Re: OT: A better way to code, by Mike Bostock

Hi Matt, thanks for sharing this! It seems that Bostock is a strong follower of Bret Victor, which I've found always quite inspiring on better ways of programming. The work at observablehq.com seems strongly focused on intensive data manipulation and

Re: A study outline containing eric6 docs

Hi all, this is an old post, but there's a related question I had no time to ask you all until now: I'm greatly interested in knowing what process do you folks follow to convert PDFs to Leo outlines? I've tried it in the past, but with mixed success. All hints will be of great help! On

Re: Please consider becoming a Leo dev, even if you aren't a programmer

Hi Edward, this is a great idea! I'll take your offer! I've been trying to get into Leo's code for some time now, so this is an opportunity I cannot miss. But what makes it a so great idea for me is that I happened to find Leo when I started a personal quest, after about 30 years of

Re: Font settings are not honored

> > Is it persistent or does it clear when you close then open the file? > OK, it clears when I close then open again the file. So these are good news. Thaks for your help! > When you press Alt it should underline the shortcut. You can also run > Alt-x, reload-style-sheets from the

Re: Font settings are not honored

Thanks Chris. FYI, this *kind of* worked for me, except for the rendering of the body pane: In fact the body pane was also

Re: Atom might be Leo's future

Regarding performance, VSCode is beating Atom by far according to Atom users themselves: https://github.com/atom/atom/issues/10188 On Wednesday, February 21, 2018 at 2:00:47 AM UTC-3, Xavier G. Domingo (xgid) wrote: > > Wow, this is amazing! I had this exact same idea about two wee

Re: Atom might be Leo's future

Wow, this is amazing! I had this exact same idea about two weeks ago, but for taking the best of Leo to VSCode instead of Atom! I've recently re-discovered VSCode thanks to a plugin made by a colleague at work and I'm nearly falling in love with it. Clean interface, quite fast (you have to try

Re: ENB: about emacs drawers

Hi Edward, I agree that issue #414 had become too long. As I already said , the proper course of action was to split that issue in various other small issues, but so far only #588 was created and I think that there's

Re: Harvesting Tips from GitHub

On Thursday, December 7, 2017 at 2:28:52 PM UTC-3, Terry Brown wrote: > I think the current GitHub solution handles revision. The harvesting > code only takes a moment to run - we could add it to a git commit hook > as a once a day thing for example. As you say re-opening an tip-issue >

Re: Harvesting Tips from GitHub

On Thursday, December 7, 2017 at 1:20:07 PM UTC-3, Terry Brown wrote: > > > I disagree. We need to define the canonical source for the tips, or > violate DRY. If we're using GitHub because of its markdown editing / > preview, I think by default GitHub is the canonical source. > > I agree

Re: Leo not starting with curses gui

El 14/08/2017 a las 19:24, lewis escribió: Is npyscreen actually required? If I do a pip list in my site-packages folder, npyscreen is not installed, yet Leo console works fine for me with Curses 2.2 installed. Here is proposed documentation for addition to Leo’s Console Gui

Re: Leo not starting with curses gui

El 14/08/2017 a las 12:09, Edward K. Ream escribió: Rev bd1de3d in master now should issue a warning if npyscreen fails. Edward Thanks Edward: I have updated to the current master and checked that effectively a clearer Warning is shown now when npyscreen is missing. But installing

Re: Leo's run levels

I'm wondering if it would be a useful thought experiment to list a series of "run levels" (https://en.wikipedia.org/wiki/Runlevel) or levels of initialization for Leo - just a textual list where we do our best to be aware of dependencies for each level. It will be interesting to look at

Re: A road to branch pollution: git stash goes back in time

El 16/07/2017 a las 15:52, Edward K. Ream escribió: On Sun, Jul 16, 2017 at 12:29 PM, vitalije > wrote: Having said that, my earlier recommendation than one should avoid switching branches in same folder is not valid any more.

Re: f302ae8 (persist branch) may fix #526. Pls test cautiously

El 14/07/2017 a las 12:20, Edward K. Ream escribió: Imo, section references is clearly the very worst idea that the usually-brilliant Donald Knuth ever had. They are wretched engineering: I read somewhere that the purpose of section references was precisely to have kinda "procedures" or

Re: Should search commands when there is no more hits return to position where search first started

El 12/07/2017 a las 21:35, lewis escribió: The search-return-to-origin command isn't working for me. I have no bindings in myLeoSettings.leo Leo Log Window Leo 5.5, build 20170712142037, Wed Jul 12 14:20:37 CDT 2017 Git repo info: branch = master, commit = 840c257d1084 Python 3.6.1, PyQt

Re: Should search commands when there is no more hits return to position where search first started

New command `search-return-to-origin` is by default bound to Alt-F3, and it will restore current position as well as outline shape (expanded/contracted state of all nodes) to the state they were when last search has started. Great idea! I'll try to test it soon. -- You received this message

Re: A road to branch pollution: git stash goes back in time

El 10/07/2017 a las 12:05, Edward K. Ream escribió: On Sunday, July 9, 2017 at 1:09:57 AM UTC-5, Edward K. Ream wrote: *Danger*: *stashing goes back in time in master*. All of Leo's caches must be completely cleared! And I just came across another danger. If I have written a file in

Re: Vote: display trailing whitespace by default?

I also vote for the Yes. Xavier El 10/07/2017 a las 11:45, Terry Brown escribió: Hi - I've added a syntax highlighting rule to Leo to display trailing whitespace, which is the default in some editors, nano for example. The trailing whitespace is shown underlined with small red dots, although

Re: How does instant update work in Pharo?

How does Pharo handle changes in object format or methods? How does Pharo recover from crashes due to changed method signatures, invalid calls, etc? Those are very good questions! From my experience, the greatest answers always come from*the best questions.* ​I'm already noticing the

Re: sqlite-format and settings - ideas

On Sat, Jul 8, 2017 at 10:43 AM, Chris George > wrote: Here is one approach to using sqlite with git. https://ongardie.net/blog/sqlite-in-git/ ​Thanks for this. And here is a stack

Re: sqlite-format and settings - ideas

From Offray: as I understand Sqlite storate will be used only for settings and from Terry: I don't think we've considered the impact of switching to a binary format *That's an important point that was not so clear until now! *At least not for me considering that Vitalije said the following at

Re: sqlite-format and settings - ideas

Ville on this counts with my "moral" support (because my technical capability is departing from Leo and Python to Grafoscopio and Pharo) and this is a worthy exploration. Advocating for a simpler Leo format has been in this forum since several years ago (YAML, JSON, etc have been in our

Re: at_clean under at_others node feature request

El 06/07/2017 a las 10:26, Josef escribió: % at_file main.tex: \section{Section level} bla bla bla \input{sub} bla bla bla ... % at_file sub.tex: \subsection{Subsection level} more bla more bla ... Thanks Josef, now I got it! And that's a kind of tree structure I had never thought about,

Re: sqlite-format and settings - ideas

I mean that it should be possible to have also a real-time settings edition experience by editing Leo outlines, shouldn't it? ​It's not that easy. Many settings affect the creation of objects.​ Sure, but which objects? I mean: I don't see why those settings affecting those objects

Re: sqlite-format and settings - ideas

I don't know any other way. Perhaps there is another and maybe even better way, but I can't imagine it. At present Leo uses same code to read user document and to read settings files. One of the settings that is very important is enabled_plugins. It can be defined in leoSettings.leo, in

Re: sqlite-format and settings - ideas

Hi Vitalije, I'm following your work in the sqlite-leo branch with great interest. Congratulations for this great idea and endeavour! Some of your ideas are being quite inspiring for me. Regarding your recent comment about simplifying Leo's init code: However, as I have stated in README of

Re: Oops: 58d7b463504 merges sqlite-format branch into master

El 04/07/2017 a las 11:52, Terry Brown escribió: I think we're ok there, the reverts that Vitalije did may have left an incomplete set of sqlite-format work master, but Edwards fix probably cleaned those out (although git revert f0a76ae might have been more thorough). And the sqlite-format

Re: at_clean under at_others node feature request

Hi there, Josef: I'm recently also trying to figure out how would some improvements to the @clean directive look like to meet my needs (somehow, but not fully, explained some time ago at my comments to this issue )... so I've found your

Re: Oops: 58d7b463504 merges sqlite-format branch into master

El 04/07/2017 a las 11:55, Terry Brown escribió: On Tue, 4 Jul 2017 09:29:01 -0500 "Edward K. Ream" <edream...@gmail.com> wrote: On Tue, Jul 4, 2017 at 7:46 AM, Xavier G. Domingo <xgdomi...@gmail.com> wrote: I think from past experience that some git corruption co

Re: Oops: 58d7b463504 merges sqlite-format branch into master

El 03/07/2017 a las 16:36, Terry Brown escribió: It seems to me that the commit that collapsed the two branches together was f0a76ae7b793e8adc2964402e86b27c4ecfef19d Author: Edward K. Ream 2017-07-03 08:56:38 Committer: Edward K. Ream 2017-07-03

Re: Rev e2cd63: curses gui ready for *careful* testing

Congratulations Edward! It's been a huge work from your side and a pleasure from our side to have you sharing with us the technical challenges and decisions made during the journey! Thanks for sharing! Xavier El 07/06/2017 a las 13:06, Edward K. Ream escribió: Recent work makes the

Re: Cross-file links

Any suggestions on how to create links to nodes in other .leo files? I've been using a simple alternative with good success since the last changes made by EKR to the handleUrl logic some months ago: just use the UNL as is but replacing "unl://" by "file://". Best regards, Xavier -- You

Re: I've declared war on fit and finish problems :-)

OK, I've created all of them: * https://github.com/leo-editor/leo-editor/issues/453 * https://github.com/leo-editor/leo-editor/issues/454 * https://github.com/leo-editor/leo-editor/issues/455 * https://github.com/leo-editor/leo-editor/issues/456 *

Re: I've declared war on fit and finish problems :-)

Another minor bug: I make a search of a text in the entire outline with the "wrap Around" option activated. I start the search in the middle of the outline, find some matches in several nodes and keep pressing F3 until I reach the end of the outline. Then the search goes on and finds some

Re: I've declared war on fit and finish problems :-)

And just right now I've come across another issue, this time is a performance one: If I make a Search and Replace of a simple string (".html" to ".htm") and press the "Replace All" button with the option "Node only" in a node with about 370 lines of text (approx. 40,000 chars) in its body, the

Re: I've declared war on fit and finish problems :-)

Oh, another one: The size of the Chapters drop-down list is not resized when new "@chapter" directives are added to headlines which are longer than the previously existing ones, so the new chapter names cannot be read: This is only fixed by closing and opening again the .leo file. Or

Re: I've declared war on fit and finish problems :-)

> This kind of fit and finish problem undermines people's confidence in Leo's overall quality. I consider all such problems to be extremely serious. That's a wise attitude. I've recently found 3 minor issues that may or may not be included in this category: 1. Focus jumps to de body pane when