Thanks Brian for your elaborate response.
Its true, in general jumps just one page, but if the body pane is a bit
bigger / smaller than X full lines (ie total length is, for instance, 12'5
lines), it jumps one line more than desirable, so you have to go back to
read it.
In the way I use Leo, I ke
On Tue, Aug 19, 2014 at 8:16 PM, Brian Theado wrote:
> A few years ago the page up/down functionality was a fixed number of
> lines. I looked into the QT cpp code and translated it to python and
> checked it in:
>
> https://github.com/leo-editor/leo-editor/commit/9401804f956c0eef31d2068450a21436e9
A few years ago the page up/down functionality was a fixed number of
lines. I looked into the QT cpp code and translated it to python and
checked it in:
https://github.com/leo-editor/leo-editor/commit/9401804f956c0eef31d2068450a21436e9939268
since then the page up/down has always been exactly a p
The completion and the function signature help work for me as you
described, but I also get the report of the unexpected exception.
You seem to have concluded that I only saw the unexpected exception.
Sorry I misled you.
--
You received this message because you are subscribed to the Google Gr
On 08/19/2014 01:49 PM, 'Terry Brown' via leo-editor wrote:
Oh, I have
@bool use_qcompleter = True
Probably not. print-settings tells me that I also have
useqcompleter = True
--
Segundo Bob
segundo...@gmail.com
--
You received this message because you are subscribed to the Google Groups
On Tue, 19 Aug 2014 13:24:35 -0700
Segundo Bob wrote:
> On 08/19/2014 11:48 AM, 'Terry Brown' via leo-editor wrote:
> > Note than you can do this(*) in Leo already:
> >
> >c.sel
> >
> > shows completions, so I select one then
> >
> >c.selectPosition?
>
> When I hit after selecting "sele
On 08/19/2014 11:48 AM, 'Terry Brown' via leo-editor wrote:
Note than you can do this(*) in Leo already:
c.sel
shows completions, so I select one then
c.selectPosition?
When I hit after selecting "selectPosition," I get the following
error message in the log pane:
Unexpected except
How cool!
On Tue, Aug 19, 2014 at 1:48 PM, 'Terry Brown' via leo-editor
wrote:
> On Tue, 19 Aug 2014 10:56:37 -0700 (PDT)
> Fidel N wrote:
>
>> Just checked again the link, and the video.
>> Cant wait to have that coded into Leo, seems so useful!!
>
> Note than you can do this(*) in Leo already:
On Tue, 19 Aug 2014 10:56:37 -0700 (PDT)
Fidel N wrote:
> Just checked again the link, and the video.
> Cant wait to have that coded into Leo, seems so useful!!
Note than you can do this(*) in Leo already:
c.sel
shows completions, so I select one then
c.selectPosition?
This second step s
Just checked again the link, and the video.
Cant wait to have that coded into Leo, seems so useful!!
On Tuesday, August 19, 2014 2:22:33 PM UTC+2, Kent Tenney wrote:
>
> Sounds like a brilliant direction to me.
> So many broad-shouldered giants out there ...
>
> On Tue, Aug 19, 2014 at 3:53 AM,
Yay, it works!
Thanks,
Kent
On Tue, Aug 19, 2014 at 11:11 AM, 'Terry Brown' via leo-editor
wrote:
> On Mon, 18 Aug 2014 15:56:31 -0500
> Kent Tenney wrote:
>
>> vanilla buttons work fine if defined in myLeoSettings.leo ...
>>
>> I'll bravely shoulder the burden of putting the rclickers in the
>
On Mon, 18 Aug 2014 15:56:31 -0500
Kent Tenney wrote:
> vanilla buttons work fine if defined in myLeoSettings.leo ...
>
> I'll bravely shoulder the burden of putting the rclickers in the
> file ;=]
:)
@rclick should work ok in settings files now too, code tidy up etc.,
quite a bit of refactori
On Tue, 19 Aug 2014 03:53:30 -0700 (PDT)
"Edward K. Ream" wrote:
> Happily, yesterday's work with k.getArg clarified the code enough
> that there is real hope that tab cycling can be restored better than
> ever.
Thanks for that :-)
Cheers -Terry
--
You received this message because you are su
On Tue, Aug 19, 2014 at 5:53 AM, Edward K. Ream wrote:
> Happily, yesterday's work with k.getArg clarified the code enough that there
> is real hope that tab cycling can be restored better than ever.
This has been a complete success, with one special case that probably
nobody will notice. Rev 3
Sounds like a brilliant direction to me.
So many broad-shouldered giants out there ...
On Tue, Aug 19, 2014 at 3:53 AM, Edward K. Ream wrote:
> On Fri, Aug 15, 2014 at 10:54 AM, Kent Tenney wrote:
>> https://srclib.org/
>>
>> Quite impressive programmer tool
>
> Thanks Kent. This is the new dir
On Monday, August 18, 2014 5:54:01 AM UTC-5, Edward K. Ream wrote:
> At present, when entering command names (but *not* file names) in the
minibuffer, hitting tab repeatedly cycles through the list of names shown.
> I would like to eliminate this "Easter Egg": it's clearly not needed and
it gre
Tried to do myself, but cant fin any binding for pgup or pgdn in either
leosettings or leopyref.
Also, found out that this wont work if the user wants to select the whole
page (shift + script) wont select the whole page, just jump.
But its good enough for reading as is.
On Tue, Aug 19, 2014 at 10
On Fri, Aug 15, 2014 at 10:54 AM, Kent Tenney wrote:
> https://srclib.org/
>
> Quite impressive programmer tool
Thanks Kent. This is the new direction for Leo: rather than doing my
own research, I'll be looking at integrating tools like srclib, Jedi
and rope into Leo.
Edward
--
You received t
On Tue, Aug 19, 2014 at 3:36 AM, Fidel N wrote:
> for number in range(c.frame.body.bodyCtrl.linesPerPage()):
> c.executeMinibufferCommand("next-line")
Excellent. This should be the default binding of the PageDn key.
Edward
--
You received this message because you are subscribed to the Go
Hi:
For those of you reading a lot in Leo it might be uncomfortable to use Page
Down/Up since it doesn't exactly jump one page, so you have to check where
you were reading each time you use that.
This script jumps exactly the number of lines in the text widget. So you
can keep reading where you
20 matches
Mail list logo
