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

Here's a common scenario. 1. I think a task is going to be easy, so I begin work on it in master. 2. Oops. The task isn't so easy. I better switch to a new branch. 3. No problem, right? Just do git stash, create the branch, and do a git stash pop. *Danger*: *stashing goes back in time in maste

Re: How does instant update work in Pharo?

On Sat, Jul 8, 2017 at 6:17 PM, 'Karsten Wolf' via leo-editor < leo-editor@googlegroups.com> wrote: > Disclaimer: This may sound like a rant but it isn't. I got out of that > rabbit hole a decade ago. For me programming in Smalltalk is dreaming of > the ideal software and programming in Python is

Re: How does instant update work in Pharo?

Disclaimer: This may sound like a rant but it isn't. I got out of that rabbit hole a decade ago. For me programming in Smalltalk is dreaming of the ideal software and programming in Python is Getting things done. >From what I have seen, Pharo is the current popular Squeak derivative. I might >b

Re: How does instant update work in Pharo?

On Sat, Jul 8, 2017 at 5:20 PM, Jacob MacDonald wrote: > Afraid not, it's firmly vaporware right now and thus I'm loath to talk > about it before I've done any actual work. > ​Hehe. I'll wait with as much patience as I can muster ;-) Edward -- You received this message because you are subscr

Re: How does instant update work in Pharo?

Afraid not, it's firmly vaporware right now and thus I'm loath to talk about it before I've done any actual work. On Sat, Jul 8, 2017 at 5:17 PM Edward K. Ream wrote: > On Sat, Jul 8, 2017 at 3:51 PM, Jacob MacDonald > wrote: > >> This mailing list keeps getting filled with things I'm otherwise

Re: How does instant update work in Pharo?

On Sat, Jul 8, 2017 at 3:51 PM, Jacob MacDonald wrote: > This mailing list keeps getting filled with things I'm otherwise > interested in, from Fossil to Smalltalk! Since the beginning of this year > I've had the idea of creating a Smalltalk environment inside Leo; Perhaps > this is the inspirati

Re: How does instant update work in Pharo?

This mailing list keeps getting filled with things I'm otherwise interested in, from Fossil to Smalltalk! Since the beginning of this year I've had the idea of creating a Smalltalk environment inside Leo; Perhaps this is the inspiration needed for me to actually put some time into it. On Sat, Jul

Re: How does instant update work in Pharo?

On Saturday, July 8, 2017 at 1:45:26 PM UTC-5, Edward K. Ream wrote: So...Could we define a PharoObject class (in Python) that could do the same? > I meant to say that if we want our app to emulate Pharo in Python all our app's objects should derive from PharoObject instead of object. Hmm. Tha

Re: How does instant update work in Pharo?

On Friday, July 7, 2017 at 5:23:21 AM UTC-5, Edward K. Ream wrote: > > I'm beginning to wonder what the difference is between the Pharo way and > #511: > reload-leo command. > > How does Pharo handle changes in object format or methods? How

Re: Experiment: use README.MD to document branches

On Sat, Jul 8, 2017 at 10:10 AM, Terry Brown wrote: > There is a simple workaround. Don't *replace* the standard readme, > > *add *the branch description *in front of* the standard readme file. > > One option: > > https://stackoverflow.com/a/3970442/1072212 > > another approach: > > https://stack

Re: sqlite-format and settings - ideas

On Sat, Jul 8, 2017 at 10:43 AM, Chris George wrote: > Here is one approach to using sqlite with git. > > https://ongardie.net/blog/sqlite-in-git/ > ​Thanks for this. And here is a stack overflow response . ​All this research is a ton of fun. Edwar

Re: sqlite-format and settings - ideas

Here is one approach to using sqlite with git. https://ongardie.net/blog/sqlite-in-git/ Chris On Sat, Jul 8, 2017 at 2:16 AM, Xavier G. Domingo wrote: > From Offray: > > as I understand Sqlite storate will be used only for settings > > and from Terry: > > I don't think we've considered the imp

Re: help with modes and key handling

Command 'edit-shortcut' is in 7142abe. Usage is like this. When editing line in `@shortcut` node or when `@command ... @key=` is selected, executing this command will wait for the next key combination to be pressed. Whatever key combination user press, that is entered in current body line (in c

Re: sqlite-leo and collecting settings

On Sat, 8 Jul 2017 08:46:07 -0500 "Edward K. Ream" wrote: > On Sat, Jul 8, 2017 at 4:53 AM, vitalije wrote: > > > > It seems that at-font settings kind is replaced with other methods > > of configuration. > > > > ​This is complicated. Iirc, the complications stem, in part, from the > theme m

Re: sqlite-leo and collecting settings

On Sat, 8 Jul 2017 00:57:14 -0700 (PDT) vitalije wrote: > I am confident that I can write command to open relevant > settings file, make change there and save it again Note that the Settings -> Edit Settings menu item machinery does some of this. Well, really it's just copying settings from on

Re: Experiment: use README.MD to document branches

On Sat, 8 Jul 2017 06:34:26 -0700 (PDT) "Edward K. Ream" wrote: > > > On Saturday, July 8, 2017 at 12:50:22 AM UTC-5, Edward K. Ream wrote: > > > > On Sunday, July 2, 2017 at 6:32:34 AM UTC-5, Edward K. Ream wrote: > > > > > Changing README.MD seems to be the simplest way to keep track of > > >

Re: sqlite-leo and collecting settings

On Sat, Jul 8, 2017 at 4:02 AM, vitalije wrote: > When user edits at-font settings node, clicking OK should adjust body of >> node to selected font. >> > > Done at 30c6dae. > Warning: previously command show-fonts expected that font family is in > clipboard and it copied selected font family in

Re: sqlite-leo and collecting settings

On Sat, Jul 8, 2017 at 4:53 AM, vitalije wrote: > It seems that at-font settings kind is replaced with other methods of > configuration. > ​This is complicated. Iirc, the complications stem, in part, from the theme machinery. @data qt-gui-plugin-style-sheet forms a "base" style, which the use

Re: Experiment: use README.MD to document branches

On Saturday, July 8, 2017 at 12:50:22 AM UTC-5, Edward K. Ream wrote: > > On Sunday, July 2, 2017 at 6:32:34 AM UTC-5, Edward K. Ream wrote: > > > Changing README.MD seems to be the simplest way to keep track of the > purpose and status of a branch. > > Alas, merging a branch into master over-w

help with modes and key handling

I have an idea how to allow user to enter shortcut in more natural way: just by hitting desired key combination. I don't know how exactly to implement it but maybe Edward or Terry would know. The idea is to create new mode: `input-shortcut`. While in this mode, every key combination should lead

Script: use git bundle to backup entire Leo repo

*Devs should never use git push --force*. Unless you you pushed sensitive data. git push --force could destroy Leo's repo. But brain spikes do happen. The following script will use git bundle to create

Re: sqlite-leo and collecting settings

While trying to test new show-fonts capabilities, I have noticed that in leoSettings.leo there are just a few at-font settings. However, when searching for at-font in Nav panel, it finds tons of settings of the following form: @string @font-... It seems that at-font settings kind is replaced

Re: sqlite-format and settings - ideas

From Offray: as I understand Sqlite storate will be used only for settings and from Terry: I don't think we've considered the impact of switching to a binary format *That's an important point that was not so clear until now! *At least not for me considering that Vitalije said the following at

Re: sqlite-leo and collecting settings

> > When user edits at-font settings node, clicking OK should adjust body of > node to selected font. > Done at 30c6dae. Warning: previously command show-fonts expected that font family is in clipboard and it copied selected font family in clipboard after dialog confirmation. Now this comman

sqlite-leo and collecting settings

Recently, I was working mostly on a leo.external.sax2db script (*part of sqlite-leo branch). Idea was to make stand-alone script that can parse xml leo document and produce sqlite db version of it. The first part of it was to transfer outline with all vnodes and their ivars including v.u. This