On Sunday, November 10, 2013 6:54:13 AM UTC-6, Edward K. Ream wrote:
> Leo now has a leoVim.py module...containing the VimCommands class.
Step 2 of the vim project is now complete. Rev 6260 contains a fairly
complete unit test of the vim scanner.
On my machine the scanner takes about 0.00
On Sun, Nov 10, 2013 at 12:39 PM, Viktor Ransmayr wrote:
> My suggestions:
>>>
>>> - Use pt for fonts; use px for borders, margins, etc.
>>> - Use 14pt as default for most panes.
>>> - Use 12pt for text in the Find Panel, and for QLabels.
>>> - Use 5px solid blue for the focus border.
>>> It's
On Mon, Nov 11, 2013 at 12:02 AM, Chris George wrote:
> Progress.
>
> Adding this to the @data qt-gui-plugin-style-sheet in myLeoSettings.leo
> adds the desired behaviour to the body pane.
>
> /* body pane border highlight */
>
> LeoQTextBrowser { border: 1px solid white }
>
> LeoQTextBrowser:foc
On Sun, Nov 10, 2013 at 7:13 PM, Brian Theado wrote:
> On Wed, Nov 6, 2013 at 1:27 PM, Edward K. Ream
> wrote:
> > It looks like the viewrendered widget doesn't handle the css properly.
> So
> > I'll test the output here:
> > http://www.w3schools.com/
On Sun, Nov 10, 2013 at 8:46 AM, Chris George wrote:
> From the Directives Reference: @file and @thin nodes are synonyms.
>
Yes. @file is preferred because it is clearer.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe f
On Sun, Nov 10, 2013 at 8:49 AM, Chris George wrote:
> The Cheat Sheet states that Ctrl-Tab performs tab-cycle-next, but the
> Command Reference contains the following:
>
> The indent-region (Ctrl-Tab) and unindent-region (Tab) commands shift
> selected lines in the body text left or right one ta
On Fri, Nov 8, 2013 at 8:53 AM, Terry Brown wrote:
> On Fri, 8 Nov 2013 06:12:49 -0600
> "Edward K. Ream" wrote:
>
>
> > And I still have no idea what the following means:
> >
> > A theme's folder should be in either .../leo/themes or $HOME/.leo/t
On Sunday, November 10, 2013 1:43:55 PM UTC-6, Edward K. Ream wrote:
>
>
> Step 2 of the vim project is now complete.
>
And 20 hours later, the framework for step 3 is in place! See rev 6265.
A recent rev added @file leoVim.py to LeoPyRef.leo, so it's now easy to see
the co
On Mon, Nov 11, 2013 at 10:33 AM, wrote:
> Hi
>
> Since there is already discussion going on about making Leo nicer out of
> the box, I will put in my two cent's worth:
> introducing a beginner's mode. I am assuming that the currently available
> mode is an advanced user's mode (which will remain
Aha 1: box cursors are easy.
There is no need to change the Qt cursor. The vim commands will simply
extend the selection range by one character. Doh! This is unlikely to
lead to substantial complications.
Aha 2: It *is* possible to use the vim keystrokes almost unchanged in Leo(!)
We certai
On Tuesday, November 12, 2013 7:30:59 AM UTC-6, Edward K. Ream wrote:
> Aha 2: It *is* possible to use the vim keystrokes almost unchanged in
Leo(!)
> '+' key is used. But just as a thought experiment, suppose it weren't.
> Then we could extend *any* single-charac
On Tue, Nov 12, 2013 at 5:30 PM, Terry Brown wrote:
> Just a heads up that caryatid on IRC (aka David Setchell) is finding
> @modes really valuable for setting up keybindings as wanted, using them
>
> as intended I guess, a tree nav. mode, etc.
>
Thanks for this. I had missed this in irc yest
On Tue, Nov 12, 2013 at 5:39 PM, gatesphere wrote:
> On 11/12/2013 6:36 PM, Matt Wilkie wrote:
>
> Edward, the way I'm seeing all these complaints about font sizes out of
> the box makes me think that the defaults should be shrunk down to 12 pt...
>
I agree.
Edward
--
You received this mes
On Tue, Nov 12, 2013 at 5:36 PM, Matt Wilkie wrote:
Not sure why 14pt-in-Leo shows so much larger than 14pt-in-others on my
> computers, but there you are. Maybe because I don't have the Deja Vu font?
>
Ah. I never thought of that. I've been concerned about the big
differences in out-of-the-bo
On Mon, Nov 11, 2013 at 11:02 AM, wrote:
> What I had in mind, however, would not be limited to a single file
> (quickstart). Rather, it would be a simplified mode of operation across the
> program. I am not clear if what you are saying is similar to this.
>
I understand the difference, but ther
Here is the checkin log for rev 6284:
QQQ
Integration of vim emulation with Leo's key handling is well underway.
Created k.getVimArg and call it where appropriate. It's now possible to
execute j k h l commands from minibuffer.
To do this, do alt-x in a file with @vim_mode = True. The minibuffer
On Wednesday, November 13, 2013 7:10:29 AM UTC-6, Edward K. Ream wrote:
> There is a new ivar, c.vimCommands, available at all times, an instance
of the VimCommands class in leoPy.leo.
I should have said, an instance of the VimCommands class **in leoVim.py**.
EKR
--
You received t
On Wednesday, November 13, 2013 7:10:29 AM UTC-6, Edward K. Ream wrote:
> As you can see, k.getVimArg knows nothing about vim commands. It calls
> vr.exec_ if vr.scan says that the minibuffer contains a complete vim
> command.
>
I forgot to mention that yesterday's w
On Mon, Nov 11, 2013 at 5:43 AM, Edward K. Ream wrote:
> On Sun, Nov 10, 2013 at 8:49 AM, Chris George wrote:
>
>> The Cheat Sheet states that Ctrl-Tab performs tab-cycle-next, but the
>> Command Reference contains the following:
>>
>
The reference is wrong. When
On Wed, Nov 13, 2013 at 8:06 AM, Kent Tenney wrote:
>
> I tend to think that a local myLeoSettings.leo file is the answer
> .
>
Ah. That's the simple way. Thanks for the suggestion.
- Create leo/beginners folder.
- In it, put a myLeoSettings.leo tailored for beginners.
- When Leo starts up,
On Wed, Nov 13, 2013 at 7:57 AM, Jacob Peck wrote:
> Pushed, rev 6286.
>
Thanks. I have it and it works as expected.
The only downside (for me) is that now I won't be able to continually
monitor the @data qt-gui-plugin-style-sheet leoSettings.leo. That is, if
I want the larger fonts (importa
On Wednesday, November 13, 2013 8:13:53 AM UTC-6, Edward K. Ream wrote:
>
> The reference is wrong. When text is selected, plain tab does
> indent-region and shift-tab does unindent-region. I'll fix this now.
>
Done on the web and on the trunk.
EKR
--
You received this me
On Wed, Nov 13, 2013 at 8:42 AM, Terry Brown wrote:
>
make an "EasyLeo
shortcut which uses
--settings=.../leo/conf
ig/simpleL
eoSettings.leo.
Nice. I've added it to the bug discussion.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group
@settings trees may now contain @outline-data nodes. These nodes, and
their descendants, can be used to pass entire outlines as the value of
c.config.getOutlineData. Details below.
Leo's abbreviation manager now uses settings of the form::
@outline-data tree-abbreviations
to create abbre
On Thu, Nov 14, 2013 at 6:46 AM, Edward K. Ream wrote:
Leo's abbreviation manager now uses settings of the form::
>
> @outline-data tree-abbreviations
>
> to create abbreviations that expand into *outlines* when they fire.
>
At present, tree abbreviations do not suppo
On Thu, Nov 14, 2013 at 7:37 AM, Jacob Peck wrote:
> This is awesome! Thanks!
You're welcome. I think so too ;-) It adds the outline dimension to
settings.
>
> Just spent some time playing with it. Aside from the pasting step, it
> seems pretty straightforward.
>
> I doubt there's a way for
On Thursday, November 14, 2013 7:29:07 AM UTC-6, Edward K. Ream wrote:
>
>
> At present, tree abbreviations do not support template patterns such as:
>
> <|url|>
>
> or
>
> {|{x=time.asctime()}|}
>
As of rev 6297, both are supported.
It wasn't pre
On Thursday, November 14, 2013 9:22:01 AM UTC-6, Edward K. Ream wrote:
> g.createScratchCommander() would indeed be good to have, because initing
it properly is non-trivial.
I have mixed thoughts about this. On the one hand, using an existing
commander should be safe. And it might actua
On Thursday, November 14, 2013 12:14:12 PM UTC-6, Edward K. Ream wrote:
As of rev 6297, both [kinds of abbreviation templates]are supported.
>
> It wasn't pretty. There may be bugs.
>
Rev 6299 contains a thorough revision of all the helpers of expandAbbrev.
This code much simpl
On Thu, Nov 14, 2013 at 7:43 PM, gatesphere wrote:
> http://www.technologyreview.com/review/520246/as-we-may-type/
>
> Found this thumbing through this month's issue of MIT Technology Review.
> An interesting look at the new paradigms in editing, and the versatility
> of outliners. No mentions
Leo's config directory now contains 4 new .leo files that illustrate how
Leo looks at various font sizes: leo10pt.leo, leo12pt.leo, leo14-12pt.leo
and leo14pt.leo.
These files contain nothing but:
- A file to monitor xxxpt appearance
- @settings
- @data qt-gui-plugin-style-sheet
It's highly
In the previous thread I discussed four new files in Leo's leo/config
directory: leo10pt.leo, leo12pt.leo, leo14-12pt.leo and leo14pt.leo.
These files are an example of an important technique, that belongs in a Leo
tips section.
The idea is to use .leo files to test settings rather than to cont
On Thursday, November 14, 2013 7:37:26 AM UTC-6, Jacob Peck wrote:
>
> I doubt there's a way for Leo to make a scratch-space outline, i.e. with
> it's own c and p definitions, that isn't saved to a file, and goes out
> of scope when a script is done running?
Rev 6300 contains g.createScratch
On Fri, Nov 15, 2013 at 7:55 AM, Jacob Peck wrote:
> My personal vote is 10pt everywhere
Thanks for your vote!
The surprising thing is how much more I am to variations in font sizes now
that there is a dead-easy way of comparing them using the pt-test .leo
files in the leo/config directory.
My test cases for the recent changes all had the node containing the
abbreviation as the last node.
If it's not, a following node will be selected.
This must be fixed today.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe
On Friday, November 15, 2013 8:11:42 AM UTC-6, Edward K. Ream wrote:
>
> My test cases for the recent changes all had the node containing the
> abbreviation as the last node.
>
> If it's not, a following node will be selected.
>
Fixed at rev 6302. This was much more eas
It would be great to have a much wider gallery of screen shots showing
different fonts, font sizes, coloring schemes, plugins, plugins etc. This
will have an immediate impact on potential Leo users.
It would be especially interesting if the screenshot illustrated different
applications for Leo
On Fri, Nov 15, 2013 at 8:27 AM, Matt Wilkie wrote:
> It's not completely reliable, not all visual settings seem to be honoured
> all the time, but I note that when opening different .leo's with different
> font settings the different sizes take effect immediately (most recent one
> opened wins).
On Fri, Nov 15, 2013 at 8:23 AM, Matt Wilkie wrote:
>
> Ditto, and for the same reasons, easier on a small screen.
>
Thanks for your vote.
I hardly ever use laptops, so your (plural) points of view were a bit
surprising. Completely understandable in retrospect.
So I'm leaning to 10pt out of t
On Fri, Nov 15, 2013 at 10:50 AM, Fidel N wrote:
> Edward:
>
> So far I am still working on the Leo interactive pane I talk about ever
> since my very first post in this group.
>
> Finally its becoming really useful, and easier to use. Still don't know if
> its useful/easy to me just because I
On Fri, Nov 15, 2013 at 10:35 AM, Terry Brown wrote:
Changing
> [settings without reloading Leo] would be a
> lot more difficult.
As a post script to the general technique, it's surprisingly useful to
have at least one *small* Leo file that you can open quickly.
I use ekr.leo, and I can open it
On Friday, November 15, 2013 10:22:39 AM UTC-6, Edward K. Ream wrote:
>
> So I'm leaning to 10pt out of the box.
>
Another alternative is 12pt for body text, tree widgets and the log pane;
10pt for everything else.
leo/config now contains leo12-10pt.leo, and I am about use thos
On Fri, Nov 15, 2013 at 11:33 AM, Chris George wrote:
>
10pt everywhere except for 12pt in the body pane.
Thanks! This is going to be close to the new default, as discussed in the
other thread.
The image looks great on my machine at 100%
Edward
--
You received this message because you are
On Friday, November 15, 2013 11:41:57 AM UTC-6, Edward K. Ream wrote:
leo/config now contains leo12-10pt.leo, and I am about use those settings
> in leoSettings.leo.
>
...
> leoSettings.leo should have disabled copies of all the
>
> @data qt-gui-plugin-style-sheet
>
>
On Fri, Nov 15, 2013 at 11:09 AM, Matt Wilkie wrote:
> Hi,
>
> Can someone point me to a working example of @menuat? I'm reading
> http://leoeditor.com/customizing.html#menuat but haven't been able to
> make it work.
>
I see on #leo that you have had success. Please echo it hear. Thanks.
EKR
I'm writing this in the middle of the night, in the hopes I can get back to
sleep ;-)
For many years I have viewed Leo's more-complex-than-vim's environment as a
hindrance to vim-like emulation.
The reverse is true!
Indeed, suppose we specify (using one or more @data nodes), normal-mode
bindi
On Saturday, November 16, 2013 3:51:43 AM UTC-6, Edward K. Ream wrote:
> 1. When focus is in the tree we could use:
>
> - j: same as Down-Arrow, goto-next-visible
> -k: same as Up-Arrow, goto-prev-visible
> -h: same as Left-Arrow, contract-or-go-left
> -l: same as Right-Ar
On Sat, Nov 16, 2013 at 3:12 AM, Matt Wilkie wrote:
> My sincere apologies to you Edward, and everyone who relies on the python
> package index versions of Leo.
>
> I just made a colossal mistake and removed the entire Leo package instead
> of just the problematic release I've been troubleshootin
On Sat, Nov 16, 2013 at 7:50 AM, Edward K. Ream wrote:
See, this is what I love about engineering:
http://leoeditor.com/Bromine.JPG
Who would imagine that chemical reactions would be the source of over a
hundred years of innovation?
This also shows the limitations of wikipedia. Contrast our
http://www.screencast.com/t/jL9C9kLNZ4
Be sure to click on the "Full Size" tab at the top of the screen to get
clearest text.
It was easy to produce with Camtasia Studio, once I let go of my
perfectionism :-)
Psychologically, it was easier to produce this "expert's" video because I
didn't hav
On Sat, Nov 16, 2013 at 11:54 AM, Fidel N wrote:
> Edward, my only suggestion to the video you just made is:
> Please make more!!
>
> Perhaphs I already forgot what being a Leo Noob is all about, but I would
> say you dont need to make any "more noob friendly" videos, in my opinion
> this video i
http://www.screencast.com/t/tEQ7brI4n6
Again, please view at full size for clearest text.
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 it, send an email
to leo-editor+unsub
On Sat, Nov 16, 2013 at 12:53 PM, wrote:
> Great !!! Thanks indeed, Edward. We newbies really need stuff like this.
>
> >All suggestions welcome
>
> The only suggestion: make more of them!
>
Done :-) http://www.screencast.com/t/tEQ7brI4n6
More are coming.
EKR
--
You received this message be
On Sat, Nov 16, 2013 at 1:53 PM, gatesphere wrote:
> On 11/16/2013 2:21 PM, Edward K. Ream wrote:
>
>> http://www.screencast.com/t/tEQ7brI4n6
>>
>> Again, please view at full size for clearest text.
>>
>> Edward
>>
>> Good tutorial, and down to
On Sat, Nov 16, 2013 at 3:13 PM, wrote:
> Excellent! These videos are what I was waiting for!
> Keep them coming please. Upload them to Youtube, if possible.
>
It should be possible, but I'm going to get them all done first.
Edward
--
You received this message because you are subscribed to th
On Sat, Nov 16, 2013 at 2:02 PM, Steve Litt wrote:
> On Sat, 16 Nov 2013 08:27:08 -0800 (PST)
> "Edward K. Ream" wrote:
>
> This was one of the best screencasts I've ever seen.
>
Wow. I didn't expect that. Thanks so much.
My one question is this: During
On Sat, Nov 16, 2013 at 2:54 PM, Brian Theado wrote:
Definitely helpful for showing an action was being performed, but I
> actually found the hotkey pictures confusing since many don't match
> default Leo settings.
>
> By default, delete-node doesn't have a binding. The plain left arrow
> key does
http://www.screencast.com/t/lUv7sgJh
This was a bit trickier than the first two.
What I've learned so far is that the audio is by far the most important to
get right. It's easy to wing it (create the script on the fly), provided
that I stop and re-record any audio flubs **at the moment they ha
On Sat, Nov 16, 2013 at 6:28 PM, Brian Theado wrote:
>
Yes, describing it as deleting is what confused me...I didn't know
about the Ctrl-Shift-X as cut keybinding. Thanks for clearing that up.
You're welcome. There's a lot to Leo that's easy to miss.
> At about the 40-45 second mark, the vi
Thanks for your recent corrections. I have the Camtasia "sources" (the
track-by-track data), so some corrections can be done easily.
Mis-labelled keys are easy to fix, as are callout extravagances. Video
blunders require full redoes, and audio flubs are in between.
Edward
--
You received t
On Sat, Nov 16, 2013 at 7:01 PM, Edward K. Ream wrote:
> At about the 40-45 second mark, the video clearly shows plain left
>> arrow while you are promoting. There are 2-3 other instances of the
>> same.
>>
>
This and the other mistakes have been fixed:
http://www.scr
On Sat, Nov 16, 2013 at 7:31 PM, Largo84 wrote:
> Thanks, Edward! These are great.
>
I'm glad you like them. I think they are what Leo has always needed.
> I use Camtasia Studio also and find it very easy to work with, good choice.
>
> Will these videos be linked from Leo's web site
> ?
>
C
On Sat, Nov 16, 2013 at 7:19 PM, gatesphere wrote:
Corrections:
> 1:30, screen says F3 when you're probably doing Ctrl+F.
>
Thanks. Good catch.
> 2:15, the screen *looks* like Ctrl+_ (underscore), but it could be the
> intended Ctrl+- (minus), it just looks very similar to underscore to me.
On Sun, Nov 17, 2013 at 3:04 AM, Matt Wilkie wrote:
> Oh my. If you have had trouble with search/replace, I wonder how many
>>> people gave up because of it.
>>
>>
> I'm one :)
>
Yikes. That's not acceptable.
I've spent the last 5+ years moving away from the mouse, but obviously that
has gone
I am shocked by the response to the Find/Replace tutorial.
Leo must have find/replace commands that newbies can use. This will be
part of Leo 4.11.1. I'd like to target this for the next week or so.
The new find replace will likely be based on scite and similar editors:
- A separate Search me
On Sun, Nov 17, 2013 at 2:20 AM, Matt Wilkie wrote:
These screencasts are fantastic Edward. So much of the documentation makes
> more sense now, seeing it performed. Thank you.
>
Thanks. I'm amazed at how easy they were to do once I got over my fears.
Clearly, Leo would have benefited from them
On Sun, Nov 17, 2013 at 2:08 AM, Matt Wilkie wrote:
> form another thread:
>
>> This opens up *all* Leo commands to vim's dot command. It's big.
>
>
Thanks for the tour :-)
> *But once the effort to learn it has been made, I know of no one who goes
> back.* -- from "Why, oh WHY, do those #?@
On Sunday, November 17, 2013 4:45:23 AM UTC-6, Edward K. Ream wrote:
> The new find replace will likely be based on scite and similar editors:
>
> - A separate Search menu.
>
Done at rev 6317. This involved moving @menu &Find from the @menu &Edit
tree to the top leve
On Sun, Nov 17, 2013 at 4:45 AM, Edward K. Ream wrote:
>
> The new find replace will likely be based on scite and similar editors:
>
> - A separate Search menu.
> - Quite possibly, a Search *tab* distinct from the Find tab.
> - Buttons in the Find/Search tabs initiate t
I'm in the midst of a grand rewrite of the find code. Long overdue, and
the *only* way to fix find-related bugs.
Please don't change the indicated files until this finishes, which will
likely be a day or two.
The rewrite should be worth any temporary inconveniences :-)
Let me know if an emerg
On Sun, Nov 17, 2013 at 10:53 AM, Edward K. Ream wrote:
>
The gui work is mostly complete.
You can see the new look at rev
26
23. The new buttons in the Find Pane don't do anything at present.
Despite being the results of about 24 hours of actual work over the last 36
hours, Le
On Sun, Nov 17, 2013 at 3:09 PM, wrote:
> Help! I messed up my UI configuration (I know this would happen, sooner or
> later :)
> Under the "stylesheet and source" branch of myLeoSettings.leo, it says:
>
> # To generate the stylesheet @data from this source,
> # use `run-script` on this node.
>
On Sun, Nov 17, 2013 at 2:59 PM, Matt Wilkie wrote:
> my avoidance of Leo's native S&R has less to do with mouse reliance than
> the extra steps.
>
Thanks for your detailed comments. I think all your points are valid.
My present plan for the new find is to have Ctrl-F put focus in the
"Find" te
On Mon, Nov 18, 2013 at 6:51 AM, Edward K. Ream wrote:
>
> First, though, I have to detour to fix an abbreviations botch that I
> recently introduced. It's horrible to search for <| pattern |>
> automatically when an abbreviation fires! Only ,, should ever do that.
&g
On Mon, Nov 18, 2013 at 7:11 AM, Edward K. Ream wrote:
First, though, I have to detour to fix an abbreviations botch that I
>> recently introduced. It's horrible to search for <| pattern |>
>> automatically when an abbreviation fires! Only ,, should ever do that.
>&g
On Mon, Nov 18, 2013 at 1:56 PM, rengel wrote:
My first impression:
>
> Leo is too hard to work with! Even seemingly simple things are way to
> complicated to figure out.
>
I agree completely. I am working on it intensely, with help from many
people.
> First: The default font size is too
On Mon, Nov 18, 2013 at 2:18 PM, wrote:
This is exactly the point that I was trying to make in my earlier posts.
>
I get it. Really.
It was quite a wake-up call when several of the usual suspects said they
never use Leo's find command!
Screencasts help two ways. They inform, and they show pe
On Sunday, November 17, 2013 4:45:23 AM UTC-6, Edward K. Ream wrote:
>
> I am shocked by the response to the Find/Replace tutorial.
>
> Leo must have find/replace commands that newbies can use...I'd like to
> target this for the next week or so.
>
Phase 1 of a g
On Tuesday, November 19, 2013 3:23:11 AM UTC-6, rengel wrote:
>
>
>
> Done at rev 6317. This involved moving @menu &Find from the @menu &Edit
>> tree to the top level of the @menus tree, renaming it, and adding these two
>> new items at the start::
>>
>> @item *help-for-find-commands
>>
On Tuesday, November 19, 2013 3:10:29 AM UTC-6, rengel wrote:
When I first tried to use find by entering Ctrl-F, I was frustrated that I
> couldn't enter anything into the Find field. Only after studying the
> documentation and watching the screencast I was able to perform a search.
> The minib
In the spirit of simplifying everything for new Leonistas, I propose the
following guidelines for the content of leoSettings.leo:
- No clones.
- No disabled nodes.
- No scripts except possibly @button buttons to help newbies. Certainly no
developer scripts of any kind.
- The "Startup" node shou
I think it is. I don't believe I've ever had more energy for Leo.
The effect of #leo and the various screencasts is, most importantly, a
stronger sense of community.
The stronger community has shifted the focus to newbies and simplicity.
For the first time in my memory, there is, in my mind, t
Alt-S is bound by default (in leoSettings.leo) to isearch-forward, a useful
command. The new Search menu destroys that binding.
There are at least three workarounds:
- Change @menu &Search to @menu Search. (Tested only on Windows)
- Move the Search menu back inside the Edit menu.
- Rename &Sear
On Tue, Nov 19, 2013 at 8:58 AM, rengel wrote:
BTW1: 'Find/Change Settings...' at the top of the 'Find' tab is redundant.
> What else should be there.
>
> BTW2: Probably more tools use 'Replace' instead of 'Change'.
>
Please make comments on the latest bzr version. Both of these have
already be
On Tue, Nov 19, 2013 at 9:01 AM, rengel wrote:
>
One more thing: It would be nice to know, HOW MANY instances a search has
found.
The find-all command does this.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this gro
On Tue, Nov 19, 2013 at 8:31 AM, Jacob Peck wrote:
>
Just one request:
>
> For *each* plugin that grabs config settings (@bool, @string, etc), be
> sure to include the *default* settings, even if your code is smart enough
> to work without it. I already do this with my plugins, as it helps the
On Tue, Nov 19, 2013 at 9:42 AM, Herve Meftah wrote:
> Hi All,
> It doesn't seem working in my script like that:
>
The @first line (or lines) must be the first lines of a node.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe
On Tue, Nov 19, 2013 at 9:24 AM, Fidel N wrote:
How about a new button in Leo (just in the top menus, perhaphs just right
> to "help") that would send the user directly to the #leo???
>
Excellent idea. Can you suggest the script?
Edward
--
You received this message because you are subscribed
On Tue, Nov 19, 2013 at 9:33 AM, rengel wrote:
>
> With the new 'Find' tab is huge problem:
>
Replacing something with nothing is a common pattern.
If you make a mistake, undo will restore everything as it was, so this is
not an overly risky command.
I do plan one change, asap, to both replace
On Tue, Nov 19, 2013 at 9:54 AM, Jacob Peck wrote:
>
g.openUrl(p)
on a node containing
::
>
@url http://webchat.freenode.net/?channels=%23leo&uio=d4";
Thanks. Creating an open-irc-leo command/button is on the list.
Edward
--
You received this message because you are subscribed to the Goo
On Tue, Nov 19, 2013 at 9:17 AM, Fidel N wrote:
[snip]
Traversing Leo outlines is not, in itself, traumatic. Many people are
familiar with outlines, even if they aren't familiar with all the data in
Leo's settings trees.
> The buttons of such gui should be able to change a few basic things fr
On Tue, Nov 19, 2013 at 9:33 AM, Kent Tenney wrote:
and it seems wrapping leoBridge() could offer
> the convenience of point and click while retaining the richness
> of @settings
>
Kent, I have no idea what you mean. When that has happened in the past,
it's sometimes been a sign of a brilliant
On Tue, Nov 19, 2013 at 10:49 AM, Kent Tenney
State of affairs
> - the settings live in a specialized Leo file
> - newbies hope for a familiar gui
> - leonistas require the power of the special settings file
>
> Maybe make a gui which reads and writes the settings file
>
> settings_bridge = leoBri
On Tue, Nov 19, 2013 at 11:27 AM, rengel wrote:
>
>
> There is no way I'm going to do any gui-based version of Leo's settings,
>> unless possibly the gui itself is generated by those same settings. In
>> theory, this could be possible, in practice, it would require an amazing
>> command of vario
On Tue, Nov 19, 2013 at 1:23 PM, Terry Brown wrote:
I'm going to bump my proposal here:
> https://groups.google.com/d/msg/leo-editor/kRChje5wkXg/XeV8DWLe7HMJ
> again - basically a config. *menu* with entries for all the common
> things like font size, font family, main colors, which jumps you to
On Tue, Nov 19, 2013 at 9:58 AM, Jacob Peck wrote:
>
Better yet, the following works like a charm:
The following makes open-irc-leo an official Leo command:
@g.command('open-irc-leo') (headline)
def openIrcLeo(event):
import webbrowser
webbrowser.open((
"yhttp://webchat.freenode.net/
>From #leo:
Revs 6332 & 6333: No clones or dead code in leoSettings.leo: structured
like an .ini file. Lol
leo/config/exampleSettings.leo contains example of settings.
Rev 6333: enables new-style find using @bool minibuffer_find_mode = False.
More work is needed, but it can be used from either th
This screencast covers all the basics of find and change:
https://www.youtube.com/watch?v=N5vRTGdA4Aw
Now that's the way to make an announcement :-)
I find that the video is initially blurry, but after a few moments it gets
much clearer.
Several things not mentioned in the video for simplicity
On Wednesday, November 20, 2013 10:03:28 AM UTC-6, Edward K. Ream wrote:
> This screencast covers all the basics of find and change:
https://www.youtube.com/watch?v=N5vRTGdA4Aw
Here is the link to the same video on screencast.com.
http://www.screencast.com/t/fkHH0uwmRAMQ
Imo, this lo
On Tue, Nov 19, 2013 at 5:06 PM, David McNab wrote:
Hi David. Good to hear from you again.
I have an outline in Leo which tangles to one or more text files. In
> OpenOffice, I have a master document which includes these text files, and
> applies a style to each of them. I used it for the first
1 - 100 of 22088 matches
Mail list logo
