Thank you, Gar! I sure understand about wanting to stay with dockless. In
fact, I delayed upgrading from V5.9 for a long time because I thought that
it required docks. But I'd have to say that I've made my peace with the
docks, even with their odd quirks.
I guess that I'll agonize over this
I should probably have started with a summary of what VR3 is all about.
Here it is.
VR3 is a re-implementation of my minor enhancement of viewrendered2 (to be
called "VR2+"). This was needed because VR2 was written for QT4 and didn't
work with QT5. Edward (@ekr) updated viewrendered to work
Hello Thomas!
VR3 plugin is very desired for me, but choosing btw vr3 and dockless I
would choose dockless. And believe that there are many such users who dont
want to struggle against strange algo of docks arrangement.
So in my opinion there's no matter would the first version of VR3 support
On Monday, March 2, 2020 at 10:59:57 PM UTC-5, Thomas Passin wrote:
>
> As I finish up the work on the Viewrendered3 plugin, I'd appreciate some
> advice on a few points.
>
A second question is about docks. At the moment, I have not got the plugin
working with the old, dockless mechanism. I
As I finish up the work on the Viewrendered3 plugin, I'd appreciate some
advice on a few points. One thing I'd like to know is whether it is
considered acceptable to place a css style sheet in the plugins directory.
I know that some plugins do put a UI definition file there.
Here's the
I believe that you need @rst in the node's headline (or in the headline of
a node higher up with less indentation in the subtree). As I recall,
having the @language directive in the body is not enough.
For VR3 - sorry, still a few things to clear up before release - I have
provided a menu to
On Mon, Mar 2, 2020 at 2:13 PM Thomas Passin wrote:
> BTW, with Restructured Text your zettels can have note boxes, sidebars,
> and tables that render well. See the attached screen shots.
>
Nifty.
Edward
--
You received this message because you are subscribed to the Google Groups
A zettel thought experiment.
I ran through an imaginary scenario for using a ZK, once it's populated. I
based this on how I use my bookmark manager. Note that my bookmark
collection does not actually have some of these headings and bookmarks.
*I have a piece of cod to cook for dinner (
Add @edit modes/php.py in leo 6.2-b1-devel.
Find "::php_lit", press F3 - "ne_start" is selected on the line where
nothing similar to search string at al.
Then do the same with --F - all matches lead to random location w/o
desired pattern.
I suspect this happens for nodes with some great number
On Monday, March 2, 2020 at 12:10:38 PM UTC-5, andyjim wrote:
>
> [snip]
> And if the system extracts the title for the heading, perhaps I need to
> copy the title into the 'body', below. Or it could even differ from the
> heading if there is any reason to do that. Can you have multiple
On Monday, March 2, 2020 at 12:10:38 PM UTC-5, andyjim wrote:
>
> In the example you posted, "Salmon with Whole Lemon Dressing" is the
> heading, and also the title in the rendered pane. But in the body pane,
> what follows the id is "Salmon Lemon Dressing", so the rendered title is
> the
On Monday, March 2, 2020 at 12:10:38 PM UTC-5, andyjim wrote:
>
> On Monday, March 2, 2020 at 10:07:00 AM UTC-5, Thomas Passin wrote:
>>
>>
>> The line of "=" characters marks a section break, the text in brackets
>> becomes the title, and the date speaks for itself. The number of "="
>>
On Monday, March 2, 2020 at 10:07:00 AM UTC-5, Thomas Passin wrote:
>
>
> The line of "=" characters marks a section break, the text in brackets
> becomes the title, and the date speaks for itself. The number of "="
> characters in a line doesn't matter as long as 1) the line starts with an
>
On Monday, March 2, 2020 at 11:13:24 AM UTC-5, andyjim wrote:
>
> On Monday, March 2, 2020 at 9:07:09 AM UTC-5, Thomas Passin wrote:
>>
>>
>> We've got that by means of the Leo outline structure. The proximity and
>> nesting of the Leo nodes fills exactly the same function.
>>
>
> Somehow I
On Monday, March 2, 2020 at 9:07:09 AM UTC-5, Thomas Passin wrote:
>
>
> We've got that by means of the Leo outline structure. The proximity and
> nesting of the Leo nodes fills exactly the same function.
>
Somehow I don't see it as quite the same thing. The outline structure is
hierarchical
On Mon, Mar 2, 2020 at 8:46 AM Thomas Passin wrote:
> I believe that this happens when you accidentally cause an event in the
> Windows cmd terminal. I'm referring to the terminal from which Leo is
> launched (i.e., with python -m leo.core.runLeo). It's not only during
> unit testing. For me,
On Mon, Mar 2, 2020 at 8:37 AM Thomas Passin wrote:
> I can confirm erratic mark disappearances. Usually they seem to persist
> through several bouts of closing and opening Leo, but I'm never sure they
> will be there.
>
Thanks for the confirmation of #1484.
Edward
--
You received this
On Mon, Mar 2, 2020 at 8:22 AM gar wrote:
> Oh couldn't even imagine. Thanks a lot, it works now!
>
You're welcome :-)
Edward
--
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
On Monday, March 2, 2020 at 10:07:00 AM UTC-5, Thomas Passin wrote:
[snip]
> I used this format to index the file for a full text search engine
> (Lucene). I like the format because it is easy to type, easy to read, and
> easy to parse. Note that this is an actual fragment from one of my
On Monday, March 2, 2020 at 9:39:07 AM UTC-5, andyjim wrote:
>
> On Monday, March 2, 2020 at 8:57:30 AM UTC-5, Thomas Passin wrote:
>>
>>
>> On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>>>
>>> And already I see that I could use a command to slap a UID into an
>>> already
On Monday, March 2, 2020 at 9:26:17 AM UTC-5, Thomas Passin wrote:
>
>
> So you will need to have some degree of consistency in the syntax and
> planning of what you write and in your working procedures.
>
Yes, I am aware that the different elements of the zettel must conform
strictly to
I believe that this happens when you accidentally cause an event in the
Windows cmd terminal. I'm referring to the terminal from which Leo is
launched (i.e., with python -m leo.core.runLeo). It's not only during unit
testing. For me, the usual case is that I want to switch to the terminal
to
I can confirm erratic mark disappearances. Usually they seem to persist
through several bouts of closing and opening Leo, but I'm never sure they
will be there.
BTW, I have set up these hot keys for marks:
F4 - go to next mark
F9 - set mark on node
F10 - clear all marks
I used these keys
On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>
> I've begun to use it.
>
> [snip]
This is quite a mind dump, and I am very hard to get along with. Oh well,
> hopefully some of this is stimulating/amusing at worst and maybe a little
> of it possibly useful at best.
>
It can
Oh couldn't even imagine. Thanks a lot, it works now!
--
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
On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>
> [snip]
>
> Eventually I hope, at least my vision hopes, to 'run the show' from inside
> the zettels. For example, I prep an external (or it can be an already
> imported file) for the leokasten and turn the parser loose on it.
On Monday, March 2, 2020 at 8:32:14 AM UTC-5, andyjim wrote:
>
> On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>>
>>
>> I think Zettelkasten people tend to say the automated UID system plus the
>> tags system fulfills the purpose of this, but I don't think it does. ...
>> The
On Monday, March 2, 2020 at 7:48:46 AM UTC-6, Edward K. Ream wrote:
>
>> --trace-coloring: js7.leokeyword 0 13 '@language js7'
>> match_at_language,colorRangeWithTag
>>
>
> Alright. I'll look into this.
>
In modes/test.py, change the string "javascript" to "test" everywhere.
On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>
> I've begun to use it.
> And already I see that I could use a command to slap a UID into an already
> existing zettel that doesn't yet have one. I can do it (and have done it)
> by making a new zettel and copy-pasting the body of
On Mon, Mar 2, 2020 at 7:34 AM gar wrote:
> Not much :-)
>
> --trace-coloring...
> @bool use-pygments : False
> @bool use-pytments-styles : True
> @string pygments-style-name: default
>
> literal
>
> --trace-coloring: js7.leokeyword 0 13
Not much :-)
--trace-coloring...
@bool use-pygments : False
@bool use-pytments-styles : True
@string pygments-style-name: default
literal
--trace-coloring: js7.leokeyword 0 13 '@language js7'
match_at_language,colorRangeWithTag
пн, 2 мар.
On Sunday, March 1, 2020 at 10:54:59 PM UTC-5, andyjim wrote:
>
>
> I think Zettelkasten people tend to say the automated UID system plus the
> tags system fulfills the purpose of this, but I don't think it does. ...
> The branched threads represented stepwise, connected thoughts, while the
>
Thanks! Will be waiting for it.
--
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
ah... Ok
Edward K. Ream 于 2020年3月2日周一 下午6:41写道：
>
>
> On Sun, Mar 1, 2020 at 7:40 AM Xu Wang wrote:
>
> >> What do you think the problem is?
>
> > I clicked "simple test cases collection" node first, so the p.h should
> be "simple test cases collection" when running the test.
>
> That's not
On Sunday, March 1, 2020 at 6:26:21 AM UTC-6, Edward K. Ream wrote:
I have been dithering about what to put in Leo 6.2. At last the guiding
> principle is clear:
>
> *Better to live with bugs than live with dubious bug fixes*
>
> As a result, I am declaring that 6.2 is code complete.
>
On Sun, Mar 1, 2020 at 6:44 AM gar wrote:
I tried to use pygments as a colorer for JS code. But encountered that when
> leo configured to use pygments - it colors any code as it was python code,
> no matter which @language is set atop of a node.
>
Thanks for this report. I have just created
On Mon, Mar 2, 2020 at 3:20 AM gar wrote:
> copy say 'modes/javascript.py' to 'modes/test.py'
> create a node with @language test (it's loaded - since it is colored and
> if make an error there - there'll be an abuse in stdout)
> write something reasonable - and get nothing highlighted.
>
> is
On Sun, Mar 1, 2020 at 10:42 PM gar wrote:
> And also, is there any hotkey to navigate among those editors?
>
Not at present. There may have been a cycle-focus command, but it was buggy
and was removed.
Edward
--
You received this message because you are subscribed to the Google Groups
On Sun, Mar 1, 2020 at 10:08 PM gar wrote:
> Recently I discovered a very useful option: add another editor pane to
> Leo. Now I can have multiple outlines open at the same moment.
> But. For 'no-docks' mode they are fixed sized and pretty narrow. I've
> found no way to resize it in a usual
On Sun, Mar 1, 2020 at 7:40 AM Xu Wang wrote:
>> What do you think the problem is?
> I clicked "simple test cases collection" node first, so the p.h should be
"simple test cases collection" when running the test.
That's not how @test nodes work. For *each* @test node, p is bound to the
copy say 'modes/javascript.py' to 'modes/test.py'
create a node with @language test (it's loaded - since it is colored and if
make an error there - there'll be an abuse in stdout)
write something reasonable - and get nothing highlighted.
is it necessary to do anything else with it?
--
You
the two test cases were all passed when I (and Edward) execute them.
The second one in my opinion should fail.
Thomas Passin 于 2020年3月1日周日 下午11:42写道：
> Maybe you overlooked it because it scrolled way off the screen, but the
> output of your test outline, when I ran it, contained this:
>
>
42 matches
Mail list logo
