quicksearch history of searches

Commit f1f4d43 adds support for search patterns history in quick search. To see it just enter 'h' as search pattern and the list of last 30 search patterns will be displayed. By clicking in any of them that search is repeated. Vitalije PS: I wished to enable accessing values of previous search

Re: quicksearch history of searches

On Mon, Jul 3, 2017 at 8:27 AM, vitalije wrote: PS: I wished to enable accessing values of previous search patterns by > pressing Alt+Up or Alt+Down or some other key combination. I have tried to > change eventFilter in quicksearch plugin but apparently that eventFilter is > not used. Suppose we

Re: sqlite-format and settings - ideas

On Sun, Jul 2, 2017 at 2:42 PM, Terry Brown wrote: On Sun, 2 Jul 2017 09:00:22 -0700 (PDT) > vitalije wrote: > > > A problem can arise when user changes any of relevant settings files: > > some .leo.db files can have outdated settings embedded. > > The arrangement that springs to mind for me is:

Oops: 58d7b463504 merges sqlite-format branch into master

I don't think I did this, although I can't be sure. Vitalije, could you please undo this? The sqlite-format should remain separate for awhile longer. Thanks. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group

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

I thought that I was merging master into sqlite-format not the other way. I am not sure how to undo it. To checkout previous commit and then to do what? On Monday, July 3, 2017 at 5:12:39 PM UTC+2, Edward K. Ream wrote: > > I don't think I did this, although I can't be sure. > > Vitalije, could y

Re: sqlite-format and settings - ideas

On Sun, 2 Jul 2017 13:44:23 -0700 (PDT) vitalije wrote: > > > > > I don't see a clear reason for all settings to be in each Leo > > outline, I think users are used to personal and default settings > > that are separate from file specific settings. > > > > Cheers -Terry > > > > That is what I

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

I am looking through git documentation to figure out how to undo. One advice I have found was to run command: ```git log --graph --oneline``` When I did this is what I get:

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

On Mon, 3 Jul 2017 08:37:34 -0700 (PDT) vitalije wrote: > I thought that I was merging master into sqlite-format not the other > way. I am not sure how to undo it. To checkout previous commit and > then to do what? > > On Monday, July 3, 2017 at 5:12:39 PM UTC+2, Edward K. Ream wrote: > > > > I

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

Google git revert :) Sent from my iPhone > On Jul 3, 2017, at 10:37 AM, vitalije wrote: > > I thought that I was merging master into sqlite-format not the other way. I > am not sure how to undo it. To checkout previous commit and then to do what? > >> On Monday, July 3, 2017 at 5:12:39 PM UTC+

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

On Mon, 3 Jul 2017 11:25:28 -0500 Edward K Ream wrote: > Google git revert :) > Sent from my iPhone Looking at gitk --all I'm not sure if this was Vitalije or you, Edward. f0a76ae looks more suspicious than any of Vitalije's commits, although I'm really not sure, gitk is a bit hard to follow in

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

I have tried two reverts and it did something. In diffs of last revert I can see my changes being marked red as deleted. I don't know if it reverted complete. I am sorry to tell but, I want be available for the next two days. I hope I didn't broke something. Vitalije -- You received this mess

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

On Mon, 3 Jul 2017 08:12:39 -0700 (PDT) "Edward K. Ream" wrote: > Oops: 58d7b463504 merges sqlite-format branch into master I've been staring at gitk until I'm cross eyed, but the more I do the less I'm sure the statement above is true. I'm not convinced there was ever any unintended merge. Ch

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

On Mon, 3 Jul 2017 12:40:25 -0500 Terry Brown wrote: > On Mon, 3 Jul 2017 08:12:39 -0700 (PDT) > "Edward K. Ream" wrote: > > > Oops: 58d7b463504 merges sqlite-format branch into master > > I've been staring at gitk until I'm cross eyed, but the more I do the > less I'm sure the statement abo

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

On Mon, Jul 3, 2017 at 2:36 PM, Terry Brown wrote: > > This is driving me nuts, I still can't work out exactly what happened > here. It seems to me that the commit that collapsed the two branches > together was > > f0a76ae7b793e8adc2964402e86b27c4ecfef19d > Author: Edward K. Ream 2017-07-03 08

Please make no changes to *any* branch for now

I am attempting to understand why code keeps changing unexpectedly. Clearing .leo/db does not completely solve all problems. It may be that #505 should be reopened, but something stranger may be happening. Perhaps pre-505 code remains in branches. Perhaps something else. Until I figure out w

Re: Please make no changes to *any* branch for now

On Monday, July 3, 2017 at 3:11:47 PM UTC-5, Edward K. Ream wrote: > > I am attempting to understand why code keeps changing unexpectedly. > I am pretty sure that rev 5c25d3f works as expected. Somehow something pretty strange happened after that. I think the best thing to do is to pretend that

Re: Please make no changes to *any* branch for now

On Mon, 3 Jul 2017 13:11:47 -0700 (PDT) "Edward K. Ream" wrote: > I am attempting to understand why code keeps changing unexpectedly. > > Clearing .leo/db does not completely solve all problems. It may be > that #505 should be reopened, but something stranger may be > happening. Perhaps pre-50

Re: Please make no changes to *any* branch for now

On Mon, 3 Jul 2017 13:35:12 -0700 (PDT) "Edward K. Ream" wrote: > On Monday, July 3, 2017 at 3:11:47 PM UTC-5, Edward K. Ream wrote: > > > > I am attempting to understand why code keeps changing unexpectedly. > > > > I am pretty sure that rev 5c25d3f works as expected. > > Somehow something pr

Re: Please make no changes to *any* branch for now

On Monday, July 3, 2017 at 3:44:10 PM UTC-5, Terry Brown wrote: > > Anyway, as long as no one uses git push --force, I don't think it's > possible to lose anything. > Right. We can't do that. This page

Re: Please make no changes to *any* branch for now

On Mon, 3 Jul 2017 15:08:57 -0700 (PDT) "Edward K. Ream" wrote: > On Monday, July 3, 2017 at 3:44:10 PM UTC-5, Terry Brown wrote: > > > > > Anyway, as long as no one uses git push --force, I don't think it's > > possible to lose anything. > > > > Right. We can't do that. > > This page >

Re: Please make no changes to *any* branch for now

On Mon, Jul 3, 2017 at 5:22 PM, Terry Brown wrote: > > I think it could have been done with git. ​Of course it could have.​ > I wonder if some variation > ​ ​ > of the above was what caused the problem in the first place - the > possibility I only just thought of being "No to all" when "Yes

Re: Please make no changes to *any* branch for now

On Monday, July 3, 2017 at 3:11:47 PM UTC-5, Edward K. Ream wrote: Until I figure out what is happening I recommend suspending *all* work on > Leo, even in branches. > With Terry's help, it appears that the master and sqlite-format branches are again safe to use. Edward -- You received this

Re: Please make no changes to *any* branch for now

On Mon, 3 Jul 2017 17:38:49 -0500 "Edward K. Ream" wrote: >   > I wonder if some variation​ ​of the above was what caused the problem > in the first place - the possibility I only just thought of being "No > to all" when "Yes to all" was more appropriate.  Wondering if that > could cause both bra

Re: Hard line wrapping

That works. Thanks again for the help, and the great editor. Really enjoying 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...@googlegrou