Re: Is it possible to add time in log pane?

On Mon, 17 Jul 2017 16:07:36 -0500 "Edward K. Ream" wrote: > On Mon, Jul 17, 2017 at 3:42 PM, Terry Brown > wrote: ​ > > ​ > it would take up a bunch of scree > ​n space. > > How about reporting just the time of the save-file command or the >

Re: Is it possible to add time in log pane?

I offten check files which be changed. Because I done the wrong thing that changed some contents before. And I can not get them back again. If save files many times, it is not clear to see which file has been saved without time. Now I identify them by .leo file. I hope to add time %H%M%S in log

Re: Is it possible to add time in log pane?

Maybe only display %H%M%S will not take many space. I think that popup tool tip is not a good way because of not clear. And perhaps the user should move mouse on several texts. 在 2017年7月18日星期二 UTC+8上午4:42:32，Terry Brown写道： > > On Mon, 17 Jul 2017 13:32:03 -0700 (PDT) > zhaohe wang

Re: Is it possible to add time in log pane?

On Mon, Jul 17, 2017 at 3:42 PM, Terry Brown wrote: ​ > ​ it would take up a bunch of scree ​n space. How about reporting just the time of the save-file command or the write-all-at-file-node command? Edward -- You received this message because you are subscribed to the

Re: How does instant update work in Pharo?

On Mon, Jul 17, 2017 at 12:32 PM, Edward K. Ream wrote: *​> ​4. Run the test, edit, repeat* ​> ​ After creating the dev node you simply run the dev script until everything works :-) The details depend on the code being developed. Otoh, we can safely assume that devs can

Re: Is it possible to add time in log pane?

On Mon, 17 Jul 2017 13:32:03 -0700 (PDT) zhaohe wang wrote: > I offten foget when I have saved some files. So if there are some > time diplay in the log pane, I think it is so better. > > wrote: base.py > wrote: test_views.py > saved: joyroost.leo > wrote: test_views.py >

Is it possible to add time in log pane?

I offten foget when I have saved some files. So if there are some time diplay in the log pane, I think it is so better. wrote: base.py wrote: test_views.py saved: joyroost.leo wrote: test_views.py saved: joyroost.leo wrote: test_views.py saved: joyroost.leowrote: models.py *for example:*

Re: New backend for Leo Cacher

Fixed at 8d6a7ab. My fault, sorry about that. Recently, I have switched to Python3, and now I am making Python2 crashers. Vitalije -- 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

Re: How does instant update work in Pharo?

On Sunday, July 16, 2017 at 10:24:51 AM UTC-5, Edward K. Ream wrote: > > developing with @button or @test already simulates instant reload pretty well. > Today, right now, Leo devs and script writers can develop python code *more *easily in Leo than in SmallTalk. After more thought, the first

Re: New backend for Leo Cacher

I got setting leoID from os.getenv('USER'): 'tbrown' reading settings in /mnt/usr1/usr1_t/Package/leo/git/leo-editor/leo/config/leoSettings.leo reading settings in /home/tbrown/.leo/myLeoSettings.leo Leo 5.5, build 20170715081418, Sat Jul 15 08:14:18 CDT 2017 Git repo info: branch = master,

Re: Leo's run levels

On Mon, 17 Jul 2017 01:41:00 -0300 "Xavier G. Domingo" wrote: > I think Terry's idea is great. I don't know how do Runlevels exactly > work in *nix OSs nor what is your idea on how to implement them in > Leo, but it occurs to me that it could even be useful to have a >

Re: New backend for Leo Cacher

On Sun, Jul 16, 2017 at 3:28 PM, vitalije wrote: Commit 0e98b2073 contains new backend for leoCache.Cacher. New code is > disabled by default by `SQLITE=False` switch in leo/core/leoCache.py > ​Thanks for this. I'll look at it asap. Edward -- You received this message

Re: Leo's run levels

On Sun, Jul 16, 2017 at 11:41 PM, Xavier G. Domingo wrote: ​>​ it occurs to me that it could even be useful to have a *g.initState* ivar ​. This would be a good idea if it phases can be defined simply. We shall see... Edward -- You received this message because you are

Re: A road to branch pollution: git stash goes back in time

On Sun, Jul 16, 2017 at 11:15 PM, Xavier G. Domingo wrote: > > Anyway, for those of you that need to *continuously work with various git > branches in parallel*, I've recently come across a better way of doing > it: Git Worktrees

Re: A road to branch pollution: git stash goes back in time

On Sun, Jul 16, 2017 at 3:52 PM, vitalije wrote: > The recovered nodes are *not* a sign of problems (any more). They could >> be called a courtesy--a note that code is different in the new branch from >> the previous branch. >> >> The acid test is to save all files