On Thursday, July 9, 2020 at 1:16:41 PM UTC-4, Thomas Passin wrote:
>
>
> Something that is not appreciated enough is that one's mental map changes
> over time, along with one's ideas about categorizing terms and ideas. And
> these apparent hierarchies are usually not
On Friday, July 10, 2020 at 11:00:51 AM UTC-4, Edward K. Ream wrote:
>
> On Thu, Jul 9, 2020 at 1:01 PM Thomas Passin > wrote:
>
> Are any links/categories stable over time? I'm constantly adding/deleting
> bookmarks. That doesn't bother me much.
>
Probably not
On Saturday, July 11, 2020 at 2:03:48 AM UTC-4, Félix wrote:
>
> I'm just learning about those @buttons by reading the mod_scripting
> 'readme' and trying to bring'em into leoInteg :
>
> ...
> I'm also reading about the @button having to be in a setting file or a
> @setting node ? but that woul
On Saturday, July 11, 2020 at 6:22:36 AM UTC-4, Edward K. Ream wrote:
>
> On Sat, Jul 11, 2020 at 5:06 AM jkn >
> wrote:
>
> QQQ
> Hi Edward
>Wow ... this goes back to ... Windows 3.0, maybe earlier? It was the
> 'only known use' of the Grey Alt key for me back then.
> There used to be a ta
On Saturday, July 11, 2020 at 6:13:03 PM UTC-4, Félix wrote:
>
> Oh - But of course, when git cloning the project master should be default,
> not devel.
>
I agree - BUT with a caveat. The usual advice is to clone the repo if we
want to use the latest development version. To that should be
Current plans are for the new parser to be in v3.9, so far as I can make
out.
On Tuesday, July 14, 2020 at 4:46:09 PM UTC-4, Brad wrote:
>
> This may be totally irrelevant, but Python is likely to get a new parser:
> https://www.python.org/dev/peps/pep-0617/
>
> Kind regards,
> Brad
>
>
> On T
On Friday, July 24, 2020 at 8:00:16 AM UTC-4, Edward K. Ream wrote:
>
>
>
> *Base all feature branches on dev*
>
> Previously, I based my feature branches on an "ekr" branch. But this
> complicates everything. Far better to base all feature branches on dev (or
> devel in Leo).
>
And remember t
On Friday, July 24, 2020 at 11:17:10 AM UTC-4, lun...@gmail.com wrote:
>
>
> I work in a bandwidth constrained environment where usually the only
> tolerable editors are text only through ssh in a terminal. vim and emacs
> fall into that category, emacs having way more features. emacs, to this
v5.9 is very old by now. I'm surprised that the Ubuntu package manager is
still providing it. The chances of troubleshooting this package are
probably small at this point.
I'd suggest installing the current version of Leo directly using pip. Make
sure that you have python 3.6+ on your system
I upgraded my Ubuntu installation, and Python 3 was upgraded from 3.7 to
3.8. After I installed it with pip3 install leo, Leo tried to start but
failed. The error message involved an xcb plugin for PyQt5.
It seems that other people had the same problem with other apps. I found a
solution at
I assumed from one of your sentences that somehow it had been provided by
apt. Probably not - I'd just been thinking that apt upgraded Python,
really.. As I just found out, a system upgrade can require a whole new
installation of Leo using pip/pip3, which brings in new versions of all
Leo's d
This teaches me not to rush to delete a branch once it's not needed any
more.
On Sunday, July 26, 2020 at 6:52:07 AM UTC-4, Edward K. Ream wrote:
>
> On Saturday, July 25, 2020 at 9:03:53 AM UTC-5, Edward K. Ream wrote:
>
> P. S. I am alarmed by the potential loss of data when merging git branche
I wonder if you are running python 2.7 (or pip for python 2.7). On my
system, I have to run pip3 and python3 to get the 3.x versions instead of
the 2.7 version. Leo 6.x versions require Python 3.x (I think), and if you
tried to run Leo with Python 2.7, you might get that kind of problem.
On T
eoff/anaconda3/bin/python
>
> and pip also comes from anaconda3
>
> On Tuesday, July 28, 2020, 7:13:30 p.m. NDT, Thomas Passin <
> tbp1...@gmail.com > wrote:
>
>
> I wonder if you are running python 2.7 (or pip for python 2.7). On my
> system, I have to run pip3 and p
4, Geoff Evans wrote:
>
> Is there a version of Qt5/PyQt5 other than (better suited than) the one
> anaconda provides?
>
> On Wednesday, July 29, 2020, 10:01:20 a.m. NDT, Thomas Passin <
> tbp1...@gmail.com > wrote:
>
>
> That's something nifty I didn't know.
Some of the plugins are awfully handy to have. If you have the patience,
you could comment out all the plugins except one at a time until you find
one that causes your problem.
On Thursday, July 30, 2020 at 3:55:57 PM UTC-4, Geoff Evans wrote:
>
> More experiments:
> python
> >>> impor
onfused because myLeoSettings.leo, which I didn't deliberately
> construct when I reinstalled, is almost as long (12000+ lines) as
> leoSettings.leo, whereas on another (OS-X) computer it is only a couple of
> hundred lines -- which I thought was the recommended way.
>
> geoff
>
On Friday, July 31, 2020 at 9:22:08 AM UTC-4, Geoff Evans wrote:
>
> Sorry to be slow, but:
> "MyLeoSettings has priority for setting something, otherwise
> LeoSettings.leo prevails."
>
> It seems to me that if I simply comment out a plugin line in
> myLeoSettings.leo, I'm turning it into a lin
You are so right about this. I use Leo a lot, and as you say, I have
worked out ways to work with it. But I don't know about many basic things
because I haven't encountered the right bit of documentation. For example,
I didn't know that would insert a new node.
Because Leo can do so many t
stays... as its ambivalent... always have
> to try it , undo, realize I wanted the other one... (with a node being
> selected, calling a command "promote" or "demote", only, has an unclear
> meaning)
> --
> Félix
>
> EDIT: TYPO
>
>
> On Tuesd
On Tuesday, August 4, 2020 at 5:05:57 PM UTC-4, Vedran Čačić wrote:
>
> Thank you all. Yes, Ctrl+R/L/U/D is very nice, _once you find it_, but
> it's completely nondiscoverable.
Well, not *completely*, since I did find them. With new programs, I
usually try to find operations and shortcuts i
On Thursday, August 6, 2020 at 7:05:11 AM UTC-4, Edward K. Ream wrote:
>
> On Tuesday, August 4, 2020 at 5:55:25 PM UTC-5, Félix wrote:
>
> > No other editor uses ctrl+u, d, l or r. But on the other hand, i dont
> know of any other outline editor 😄
>
> As an historical note, the MORE outliner
>
The editor component is a Microsoft project called Monaco -
https://github.com/microsoft/monaco-editor
Monaco itself can do code folding. Maybe it would be easier to find the
code in its code base than in vscode's.
On Tuesday, August 11, 2020 at 12:45:42 PM UTC-4, Edward K. Ream wrote:
>
> Yes
Here's someone who re-implemented Origami. Here he talks a bit about how
folding was implemented (double-linked n-trees) -
http://wotug.org/parallel/tools/editors/folding-editors/fe-mh/README.html
If you go to the parent directory, you can get the entire source (in C,
apparently from 1997).
O
The VR3 plugin can display the diagram outputs. It wouldn't update
automatically when you made a change - you would have to refresh the plugin
view to see that changed image.
It *may* be possible to get mermaid to run in a panel inside Leo. It could
be launched using graal, and Leo can be mad
You aren't doing anything wrong, but it shouldn't be happening. I don't
lose my clones that way. I happen to be on the devel branch but I don't
think that's a factor here:
Leo 6.3-devel, devel branch, build 6a92120f1a
2020-06-23 09:38:53 -0500
Python 3.8.2, PyQt version 5.14.2
Windows 10 AMD64
On Thursday, August 13, 2020 at 1:39:17 PM UTC-4, k-hen wrote:
>
> I don't mind refreshing at all. Pardon the naive question, but how would I
> go about trying VR3?
>
You edit the MyLeoSettings.leo file, which you can open from Leo's Settings
menu. Find a node titled @enabled plugins. Commen
On Thursday, August 13, 2020 at 10:00:49 AM UTC-4, k-hen wrote:
>
> I understand, I thought view-rendered may have been a qt html panel but I
> suppose it's rich text or something like that.
> The integration project seems very interesting ... I'll keep an eye on it
> - thanks!
> (and Leo of
rmaid node type to
viewrendered3 if you decide that Leo is promising enough for your project.
It looks like it might be something that I'd like using myself.
On Thursday, August 13, 2020 at 1:32:49 PM UTC-4, Thomas Passin wrote:
>
> The VR3 plugin can display the diagram ou
On Thursday, August 13, 2020 at 1:34:55 PM UTC-4, k-hen wrote:
>
> This is very helpful, thank you. I think using including images would be
> fine, I'm also flirting a bit with maybe trying out the leo asciidoc system
> over markdown and/or rst - which I have a harder time connecting with.
> If
Is it correct that you only are seeing this behavior on (a?) auto-md file?
On Thursday, August 13, 2020 at 5:46:36 PM UTC-4, k-hen wrote:
>
> Hi Felix,
> I am also perplexed. Note that the clones which are not a descendant of
> the file don't have this behaviour either.
>
> I first encountered th
at 6:28:00 PM UTC-4, Thomas Passin wrote:
>
> Is it correct that you only are seeing this behavior on (a?) auto-md file?
>
> On Thursday, August 13, 2020 at 5:46:36 PM UTC-4, k-hen wrote:
>>
>> Hi Felix,
>> I am also perplexed. Note that the clones which are not a de
On Thursday, August 13, 2020 at 6:22:54 PM UTC-4, k-hen wrote:
>
> Ok, thanks! I've got this going, the docks feature is interesting.
> Strangely I can move the body and the tabs, but not the VR3 panel...
> I've tried restarting & redragging it a few times but still no luck :-/
>
Add a node with
You need to have Docutils installed to have VR3 render Restructured text,
and you need Markdown installed to render (no surprise here) markdown.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving ema
On Thursday, August 13, 2020 at 7:01:56 PM UTC-4, k-hen wrote:
>
> This worked! I was able to get it for a new test file BUT the
> original file has VR3 docked *inside* the body and I can't seem to detach
> it.
> It seems these settings are on a per-file basis, but there's nothing I can
Why is it that you want to use auto-md trees? You could consider
ReStructured text, for example.
On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote:
>
> Well, Glad I'm in good company :-)
>
> I'm thinking the workaround is to use a the full path for every @auto
> headline, rather than
On Thursday, August 13, 2020 at 7:31:02 PM UTC-4, k-hen wrote:
>
> [snip]
>
Would you file a bug issue on this? The issue URL is
https://github.com/leo-editor/leo-editor/issues
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe f
On Friday, August 14, 2020 at 10:17:20 AM UTC-4, k-hen wrote:
>
> Thank you kindly for your reply. I've enabled this feature and it seems
> very promising, but I think I might need a slightly different behaviour.
> I'll take a minute to explain the use case.
>
> [snip]
> This is likely the des
I've done that a few times without trouble. First thing I would try is to
change to @file and save. Once that works, try the change to @clean.
If it still doesn't work, create a new @clean node, copy the subtree to it,
delete the (now empty) @auto node, and see if it saves. If not, there
mig
For an @file tree, you have to have the external file available in the
right place, or Leo won't have anything to read. All the structure (and
text) is stored in the external file, and it all has to be read for Leo to
(re)create the tree. With an @clean tree, the structure and text is stored
On Saturday, August 15, 2020 at 9:26:09 AM UTC-4, Edward K. Ream wrote:
>
> On Fri, Aug 14, 2020 at 11:49 AM k-hen > wrote:
>
>> Hi guys,
>> I'm trying to change and @auto node to an @clean node, but I'm getting
>> and error writing the file.
>
>
> Make sure the root node (@auto, @file, @clean)
It's what we were saying the other day. If you want to have child nodes,
you need to put a line
@others
in the parent where you want the "others" - that is, the child subtree - to
show up in the external file. And, most useful for Python programming, if
the "@others" is indented, then the li
'm blind.
>
Here's one alternative, depending on what you want to achieve:
https://github.com/leo-editor/leo-editor/issues/1611
>
>
>
>
>
>
>
>
>
>
> On Sun, 2020-08-16 at 09:13 -0700, Thomas Passin wrote:
>
> It's what we were saying the o
I want to do a search-and-replace of text in a number of nodes (or all of
them), but the replace-all command doesn't seem to do anything. I can do
Find (), and time after time to replace each occurrence,
but not all at once. What am I not knowing to do?
Similarly, if I create a path node for
single
command.
On Monday, August 17, 2020 at 6:36:02 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Sun, Aug 16, 2020 at 10:06 PM Thomas Passin > wrote:
>
> > I can't work out how to get each node to populate with the contents of
> the file that's already there.
You could, however, use a new meaningless user name in Leo. That should
have the effect you want. It will still have the date, but the name
wouldn't disclose anything.
On Monday, August 17, 2020 at 9:59:56 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Mon, Aug 17, 2020 at 7:40 AM k-hen >
> wrote
On Monday, August 17, 2020 at 9:49:13 AM UTC-4, Edward K. Ream wrote:
>
> I would like a regex that finds complete and *disjoint *typescript
> multiline block comments
>
> The following does not work, because the flags do not play well together.
>
> re.compile(r'(/\*.*?\*/)(.*)', re.DOTALL | re.M
Nested comments aren't allowed in js and ts, are they?
On Monday, August 17, 2020 at 10:53:37 AM UTC-4, vitalije wrote:
>
> re.compile(r'(/\*(:?.*?)\*/)')
>
> The inner comment text must be grouped separately to be able to apply *?
> operator on just the inner characters. Without this grouping, *
"When you use an regex to solve a problem, then you have another problem".
On Monday, August 17, 2020 at 11:35:08 AM UTC-4, vitalije wrote:
>
>
>
> On Monday, August 17, 2020 at 4:59:39 PM UTC+2, Thomas Passin wrote:
>>
>> Nested comments aren't allowed i
17, 2020 at 11:04 AM Thomas Passin > wrote:
>
>> "When you use an regex to solve a problem, then you have another problem".
>>
>
> This aphorism is misleading. Believing it was one of the worst mistakes I
> have made in my coding career. regex's a
I'd go for that. PRs, I have noticed on other projects, can support a good
discussion before the thing is finalized.
On Monday, August 17, 2020 at 12:28:58 PM UTC-4, Edward K. Ream wrote:
>
> The days of cowboy commits are coming to an end.
>
> In future, I plan to create a PR for all my work. A
ike: http://cyan4973.github.io/xxHash/ or
> https://github.com/google/farmhash
> They also have Python libraries, e.g. https://pypi.org/project/xxhash/ &
> https://pypi.org/project/pyfarmhash/
>
>
>
>
> On Mon, 2020-08-17 at 07:05 -0700, Thomas Passin wrote:
>
> You
No. But you can create a separate tree, not an @anything external file,
with clones of all the nodes you want to document, and add documentation
nodes there.
On Tuesday, August 18, 2020 at 7:13:19 PM UTC-4, k-hen wrote:
>
> Given an @clean node, is it possible to mark certain node to be exclu
Try to find a way to only add a small number at a time, then save.
Eventually you should learn how to avoid the errors, and then you won't
have the problem.
On Thursday, August 20, 2020 at 2:06:45 PM UTC-4, k-hen wrote:
>
> Hi,
> Just wondering - Is there perhaps a way to interrupt Leo without
Please describe exactly what you are doing. See if you can come up with a
very condensed example (a small file with only a few nodes, for example).
What do you want to achieve, what did you expect, and what actually
happened?
Bear in mind the the entire Leo code base is contained in a few Leo
>> > Under windows, its in your clipboard so you can just CTRL+V to paste
>> > right in here while you type. Like this:
>> >
>> > (In linux its put into your home/picture folder. )
>> >
>> > So I would recommend you paste one before, and a
I have been upgrading vr3 to render asciidoc nodes, mostly because of
Kevin's interest. The work is not finished, but at least vr3 will render a
single node of asciidoc. Because it is still in progress I haven't issued a
PR. But you can get it from my github repo -
https://github.com/tbpassin
And after I said this is a good idea, I just accidentally merged my changes
to VR3 to upstream/devel instead of origin/devel. Grrr. No harm done, I
think, because these changes were the ones that start to add asciidoc
rendering, and they work on my computer at least. They don't change any
ot
I'm doubtful about Leo-as-a-database as a replacement for a conventional
rdbms, because of the need for atomic transactions. That has always take
a lot of care in design and implementation of the code. Of course, we
don't know what Speed has done, and maybe you don't need such capabilities
a
> the Leo nodes and their non-Leo counterparts.
>
> I can think of arguments for both based on different circumstances, but
> initially at least, my preference would probably be the former.
>
>
>
>
>
> On Fri, 2020-08-21 at 08:21 -0700, Thomas Passin wrote:
> >
t;%1"
I used the expanded form in the example outline because it shows more
clearly what the elements of the command are.
On Friday, August 21, 2020 at 3:03:16 PM UTC-4, Thomas Passin wrote:
>
> If you are willing to use a command line interface to your database, like
> mysql.e
I've moved this work to a new branch on my repo - the vr3-asciidoc branch.
It's at
https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc
Please get vr3 from there if you want to try the latest efforts.
On Thursday, August 20, 2020 at 6:34:14 PM UTC-4, Thomas Passin wrote:
>
My keyboard, which is fairly new, doesn't emit , which is
very annoying. I have to use the menu to get the command. Maybe you have
a keyboard issue?
On Friday, August 21, 2020 at 8:42:16 PM UTC-4, k-hen wrote:
>
> It's very boring so far, just getting started :-)
>
> The biggest helper for now
I'm not crazy about bureaucracy, but I have noticed that the PR can lead
to a lot of good discussion, and what gets added in the end may not be
exactly what was in the PR at the start.
On Friday, August 21, 2020 at 8:55:30 PM UTC-4, Offray Vladimir Luna
Cárdenas wrote:
>
> Lunzer,
>
> I may sh
I've read some posts that people have been having unresponsive key troubles
with various Logitech keyboards (mine is a Logitech wireless), but not
always the same key(s).
On Saturday, August 22, 2020 at 8:51:57 AM UTC-4, k-hen wrote:
>
> To confirm, I just tried these (Ctrl+Shift+C & Ctrl+Shift+
ug 21, 2020 at 9:36 PM Thomas Passin > wrote:
>
>> I'm not crazy about bureaucracy, but I have noticed that the PR can lead
>> to a lot of good discussion, and what gets added in the end may not be
>> exactly what was in the PR at the start.
>>
>
> Imo, &
As long as we're on the subject, someone made some changes to viewrendered3
*in my github repo* that I didn't know about. There is a syntax error in
these changes, and I *think* something else got inadvertently changed, and
I will have to fix that up, too. Now if they had put in a PR, it would
Would you please explain what you did that got the unbindings to work? It
might help other people.
On Saturday, August 22, 2020 at 1:13:57 PM UTC-4, k-hen wrote:
>
> I use and am big fan of these :-)
> https://www.microsoft.com/accessories/en-ca/products/keyboards/sculpt-ergonomic-desktop/l5v-
1:31:00 PM UTC-4, Thomas Passin wrote:
>
> As long as we're on the subject, someone made some changes to
> viewrendered3 *in my github repo* that I didn't know about. There is a
> syntax error in these changes, and I *think* something else got
> inadvertently changed,
:14:34 PM UTC-4, Thomas Passin wrote:
>
> It looks like the changes to vr3 came via a change in the devel branch,
> and those must have come from leo-editor's devel branch. So it probably
> wasn't someone changing my repo directly. Still, there should have been
>
I noticed a .orig file show up in one of my development folders this week.
I think it was put there by some editor I don't normally use, like atom or
pyzo, which I might have used once in a while to look at at a file. But I
never staged it out to be committed and pushed - or so I thought. I
h
Don't forget, viewrendered3 already uses @rst, @md, and @asciidoc. Please
don't make these mean something else.
On Monday, August 24, 2020 at 10:36:54 AM UTC-4, vitalije wrote:
>
>
>
> On Monday, August 24, 2020 at 3:15:50 PM UTC+2, k-hen wrote:
>>
>>
>> Pardon the beginner question, but are you
Outline/"Expand/Contract"/"Contract Node".
On Monday, August 24, 2020 at 11:40:14 AM UTC-4, k-hen wrote:
>
> Is there an option or function for Leo to contract all descendants of the
> selected node?
>
> e.g. if use this option on B, then D would collapse as well, but not G.
> Collapse other nod
So you want "contract this node and all subtrees"?
On Monday, August 24, 2020 at 12:47:48 PM UTC-4, k-hen wrote:
>
> That doesn't seem to be exactly what I'm looking for, when you expand it
> again, its children are still expanded :-/
>
>
> On Monday, August 24, 2020 at 11:57:18 AM UTC-4 tbp1...@
It would help if you could be more informative about what you are trying to
accomplish. Reading what you wrote below, it sounds like you want to make
a little markup language for Markdown. Maybe you can just use Markdown
itself (or asciidoc).
If you put some special character or term into hea
So let me see if I am getting some kind of a handle on this. The following
will not be complete; it's just responding to some of the elements.
1. *You need to produce documentation to fit some template not of your
choosing, probably in markdown or similar.*
The template is not the way you
#x27;ll keep plugging and can development something on my own, just
> thought you guys might know better and/or have some ideas kicking around :-)
>
>
> 1: Define & Document the "Model" (Types + Content)
> 2: Transform/Link the Model to Code (files)
> 3: Transfo
ernal files - @clean
files inside Leo so others can edit them if needed. Leo can still
coordinate the output generation, but preferably by running external files
that others can run if you are not available.
On Tuesday, August 25, 2020 at 4:14:19 PM UTC-4, Thomas Passin wrote:
>
> I wonde
I think that if a copy of the current list of all positions were included
in the undo data, then it could be restored upon undo and everything would
work. I don't know if that would be too slow, so that it would affect the
perceived speed of the keystrokes.
On Wednesday, August 26, 2020 at 10:
:
>
>
>
> On Wed, Aug 26, 2020 at 10:11 AM Thomas Passin > wrote:
>
>> I think that if a copy of the current list of all positions were included
>> in the undo data, then it could be restored upon undo and everything would
>> work. I don't know if that would
Matt, your contributions and tact will be missed until you feel like
returning.
On Wednesday, August 26, 2020 at 7:20:53 PM UTC-4, Matt Wilkie wrote:
>
> Hello Edward and Leo community,
>
> As you've noticed I've kind of dropped out of Leo participation this
> summer. My life seems to have arriv
I am so fed up with --use-docks that I've given up on it and gone back to
the older no-docks configuration. With docks, I can never count on the
panes being the same next time I re-open an outline or restart Leo.
Sometimes they are hard to restore to my liking, too. Especially during
plugin d
I've issued a PR for VR3, and otherwise it is available from my Git repo on
the vr3-asciidoc branch -
https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
The processing for Asciidoc has been upgraded to be on a par with
reStructured Text and Markdown. This means that it handles render
I would have moved it by collapsing the node, then until it was
under the intended parent, then to make it a child of the target.
I'm not saying you did it "wrong", just that this is the sequence that
seems simplest and has always worked well for me.
On Wednesday, September 2, 2020 at 9:14:1
On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin wrote:
>
> I've issued a PR for VR3, and otherwise it is available from my Git repo
> on the vr3-asciidoc branch -
>
> https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc/leo
>
> I have found t
own
if no one knows about it.
On Wed, 2020-09-02 at 12:37 -0700, Thomas Passin wrote:
>
>
>
> On Tuesday, September 1, 2020 at 11:16:24 AM UTC-4, Thomas Passin wrote:
>
> I've issued a PR for VR3, and otherwise it is available from my Git repo
> on the vr3-asciidoc branc
On Thursday, September 3, 2020 at 7:20:39 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Wednesday, September 2, 2020 at 10:30:08 PM UTC-5, Thomas Passin wrote:
>>
>> I've just submitted a pull request for viewsarendered3 v3.0b14
>>
>
> I'
I am so opposed to webassemblies that I don't want to work on them. Web
assemblies if widespread will encourage the trend towards breaking the web
by making URLs meaningless, and will promote more closed silos and data
hiding. I do see that they could be very good in non-web use, but that's
n
On Thursday, September 3, 2020 at 10:59:41 AM UTC-4, Edward K. Ream wrote:
>
>
>> Actually, I knew about it. I'm not sure if it's real or something that
>> pylint doesn't understand (I think it's this).
>>
>
> If it's a pylint mistake, please disable the message.
>
I will once I'm sure. I pu
On Thursday, September 3, 2020 at 11:00:48 AM UTC-4, Edward K. Ream wrote:
>
>
>
> On Thu, Sep 3, 2020 at 7:41 AM Thomas Passin > wrote:
>
>> I am so opposed to webassemblies that I don't want to work on them. Web
>> assemblies if widespread will encourage
Yes, that's so, and I understand that web assemblies are basically a Google
effort to do that.
On Thursday, September 3, 2020 at 11:20:12 AM UTC-4, lun...@gmail.com wrote:
>
> You're giving technology and standards too much credit. Corporations are
> going to create closed systems and implement
release it as a non-beta release. In the meantime,
this version is V3.0b15.
On Thursday, September 3, 2020 at 11:08:04 AM UTC-4, Thomas Passin wrote:
>
>
> On Thursday, September 3, 2020 at 10:59:41 AM UTC-4, Edward K. Ream wrote:
>>
>>
>>> Actually, I knew about
There is a new boolean setting that controls whether a node's headline will
be inserted into the rendering as a top-level header. The new setting is:
@bool vr3-insert-headline-from-node
I have submitted a PR for this change,and it is also available from my
GitHub fork in the devel branch at
h
Having them be resizable - the divider between panes being movable - would
be important even if the pane layout were fixed.
On Saturday, September 5, 2020 at 7:51:04 AM UTC-4, Edward K. Ream wrote:
>
> On Friday, August 28, 2020 at 4:34:25 AM UTC-5, Edward K. Ream wrote:
>
> > I use the legacy la
There's a hindrance in this new code. Say I have 4 outlines open. I run
Leo with --init-docks and adjust one after another until the tabs are the
way I want for all four outlines. Then I close Leo and re-open if with
--use-docks. All four outlines open and have the same layout as when I
clo
Also, Add/Delete Body Editor doesn't work any more, at least with
--use-docks. I would be good if it could.
On Sunday, September 6, 2020 at 8:00:02 PM UTC-4, Thomas Passin wrote:
>
> There's a hindrance in this new code. Say I have 4 outlines open. I run
> Leo with --in
On Monday, September 7, 2020 at 9:22:57 AM UTC-4, Edward K. Ream wrote:
>
>
> You can specify the desired layout of new outlines as follows:
>
> - Open some file, say x.leo, with --init-docks.
> - Open a new file. Set the layout as you like.
> - Close the new file.
> - Save x.leo.
>
> After this, o
just unworkable as it is. Not that I have any useful
suggestions myself. I don't have a clue about how this all works.
On Monday, September 7, 2020 at 10:09:59 AM UTC-4, Thomas Passin wrote:
>
> On Monday, September 7, 2020 at 9:22:57 AM UTC-4, Edward K. Ream wrote:
>>
>>
Ah, I see. Add/Delete Body Editor with --use-docks did open/close a new
editor, but it was so tiny I didn't see it, free-floating in the upper
left, and this tiny window could not be moved or resized.
On Sunday, September 6, 2020 at 8:02:26 PM UTC-4, Thomas Passin wrote:
>
> Also,
Leo 6.3-devel, devel branch, build 65ecc3ff0d
2020-09-09 18:48:47 -0400
Python 3.8.2, PyQt version 5.15.0
Windows 10 AMD64 (build 10.0.18362) SP0
Open Leo with workbook.leo with --use-docks. Observe the correct pane
layout from previous run. Create new outline using File/New. Observe the
new
201 - 300 of 1663 matches
Mail list logo
