I'm not crazy about bureaucracy, but I have noticed that the PR can lead
to a lot of good discussion, and what gets added in the end may not be
exactly what was in the PR at the start.
On Friday, August 21, 2020 at 8:55:30 PM UTC-4, Offray Vladimir Luna
Cárdenas wrote:
>
> Lunzer,
>
> I may
My keyboard, which is fairly new, doesn't emit , which is
very annoying. I have to use the menu to get the command. Maybe you have
a keyboard issue?
On Friday, August 21, 2020 at 8:42:16 PM UTC-4, k-hen wrote:
>
> It's very boring so far, just getting started :-)
>
> The biggest helper for
Lunzer,
I may share the Fossil comments, as I'm an avid user of it. Paraphrasing
Conway's Law[1] culture and infrastructure reflect each other and I
think that Git reflect the bureaucracy of Linux Kernel development with
its fork and PR by default, while Fossil considers a small group of
It's very boring so far, just getting started :-)
The biggest helper for now are the paste-node and paste-node-as-clone which
don't seem to be working for me,
and Ctrl+n doesn't seem to unbind either, i.e. after setting to None.
I've check-bindings and they seem like they're free.
The others
I've moved this work to a new branch on my repo - the vr3-asciidoc branch.
It's at
https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc
Please get vr3 from there if you want to try the latest efforts.
On Thursday, August 20, 2020 at 6:34:14 PM UTC-4, Thomas Passin wrote:
>
> I have been
For those familiar with mysql, the following line in the launcher batch
file will also work. You don't have to put the password into the batch file
(a good thing), but you will have to type the password on the console every
time you run it (could get tedious) -
@mysql -u root -p <"%1"
I used
On Fri, Aug 21, 2020 at 3:01 PM lun...@gmail.com wrote:
> @offay, I've seen similar comments on the Fossil forums.
>
> I don't have faith in developers to write "good commit messages".
>
Imo, commit messages usually only need to be a readable tag. There are
exceptions, but they are few.
Let's
Very cool - sounds like something I'll be using soon then - thanks!
On Friday, August 21, 2020 at 3:16:06 PM UTC-4 vitalije wrote:
> leo-ver-serv will store all the history of Leo files in the sqlite3
> database files named after the original Leo files, just with added
> '.history'. If for
Very cool, can't wait to check it out - thanks!
On Friday, August 21, 2020 at 3:03:16 PM UTC-4 tbp1...@gmail.com wrote:
> If you are willing to use a command line interface to your database, like
> mysql.exe, then it can pretty easy. You put your sql into a txt file, and
> launch it with a
@offay, I've seen similar comments on the Fossil forums.
I don't have faith in developers to write "good commit messages". You need
only see this comic to understand my feelings: https://xkcd.com/1296/ .
Developers (in general) are lazy, and this is not entirely caused by
"laziness", but
leo-ver-serv will store all the history of Leo files in the sqlite3
database files named after the original Leo files, just with added
'.history'. If for example you edit workbook.leo file, leo-ver-serv will
store changes to workbook.leo.history in the same folder.
Vitalije
On Friday, August
If you are willing to use a command line interface to your database, like
mysql.exe, then it can pretty easy. You put your sql into a txt file, and
launch it with a batch file. You can create a menu item to run the
launcher in a new "Open With" menu item by adding a new setting in your
Excellent, I'll check it out - thanks! - do you happen to know if that
history_tracer works with the sqlite/db back-end?
Re: interrupt, that's great news too - in addition to just Leo functions,
if/when I get database queries working, being able to cancel the command is
a relatively critical
Intriguing ... can't wait!
On Friday, August 21, 2020 at 12:53:30 PM UTC-4 Edward K. Ream wrote:
> On Fri, Aug 21, 2020 at 9:38 AM k-hen wrote:
>
> I know this issue has been put to bed and is extremely unlikely to happen,
>> but just one more thing:
>> If I had a magic wand:
>>
>> I could add
On 17/08/20 11:28 a. m., Edward K. Ream wrote:
> The days of cowboy commits are coming to an end.
>
> In future, I plan to create a PR for all my work. A PR is a good
> record of what has been done, and it should help prevent unwanted
> merge conflicts.
>
> I think separate PR's for all work
On Friday, August 21, 2020 at 4:08:35 PM UTC+2, k-hen wrote:
>
> Thank you for the import script and the responses.
>
> I feel like maybe I'm missing something with @nosent though, why is it
> much harder to use?
>
> Let's say I have a directory of files that are each templated, i.e.
>
On Friday, August 21, 2020 at 4:14:43 PM UTC+2, k-hen wrote:
>
> Yes, absolutely, I'm a huge proponent of Git and it's toolchain :-)
> That said I want my personal comments and notes and settings *outside* of
> git and not checked in as well.
> So I need both regular backups/protection for Leo
On Fri, Aug 21, 2020 at 9:08 AM k-hen wrote:
I feel like maybe I'm missing something with @nosent though, why is it much
> harder to use?
>
Clones are fragile in @auto trees, even when @persistence is enabled.
Also, so-called cross-file clones can be problematic, due to a fairly nasty
version
On Fri, Aug 21, 2020 at 9:40 AM k-hen wrote:
> Not to pester, but some of my shortcut keys still aren't working and
> having them could save me a tremendous amount if time.
> If there's anything you could point me to, I'd really appreciate it :-)
>
Please send me your myLeoSettings.leo file.
On Fri, Aug 21, 2020 at 9:38 AM k-hen wrote:
I know this issue has been put to bed and is extremely unlikely to happen,
> but just one more thing:
> If I had a magic wand:
>
> I could add a decorator to *alias* a node's gnx, so the gnx could stay
> as-is, but I could give it an
Yes, that's true, and just to be clear, that's not what I'm suggesting
or expecting :-)
What I want is to use Leo to build the *code* that
constructs/populates/queries a separate 'proper' database.
One option is just to have Leo remain in Sqlite (and allow some basic
querying that way), but
I'm doubtful about Leo-as-a-database as a replacement for a conventional
rdbms, because of the need for atomic transactions. That has always take
a lot of care in design and implementation of the code. Of course, we
don't know what Speed has done, and maybe you don't need such capabilities
Is there *anything* I can do to help entice him?
Please Speed, please - if you're reading this, I'd *love* to see what
you've done,
it sounds incredible to me and it could really make a big difference to me
to be able to use and build on your amazing work.
I do a lot of database development
Not to pester, but some of my shortcut keys still aren't working and having
them could save me a tremendous amount if time.
If there's anything you could point me to, I'd really appreciate it :-)
On Monday, August 17, 2020 at 5:31:33 PM UTC-4 k-hen wrote:
> Hi,
> I do see this issue:
I know this issue has been put to bed and is extremely unlikely to happen,
but just one more thing:
If I had a magic wand:
I could add a decorator to *alias* a node's gnx, so the gnx could stay
as-is, but I could give it an alternate/external name as well.
So if/when the file write happens it
On Fri, Aug 21, 2020 at 9:14 AM k-hen wrote:
> Yes, absolutely, I'm a huge proponent of Git and it's toolchain :-)
> That said I want my personal comments and notes and settings *outside* of
> git and not checked in as well.
> So I need both regular backups/protection for Leo in _addition_ to
This is so awesome - thank you! :-D
On Thursday, August 20, 2020 at 7:06:39 PM UTC-4 Edward K. Ream wrote:
> On Thu, Aug 20, 2020 at 5:34 PM Thomas Passin wrote:
>
>> I have been upgrading vr3 to render asciidoc nodes, mostly because of
>> Kevin's interest. The work is not finished, but at
Yes, absolutely, I'm a huge proponent of Git and it's toolchain :-)
That said I want my personal comments and notes and settings *outside* of
git and not checked in as well.
So I need both regular backups/protection for Leo in _addition_ to the Git
repo which is synced with other devs.
On
Thank you for the import script and the responses.
I feel like maybe I'm missing something with @nosent though, why is it much
harder to use?
Let's say I have a directory of files that are each templated, i.e.
possibly having a header and footer.
These files are checked into git and
And after I said this is a good idea, I just accidentally merged my changes
to VR3 to upstream/devel instead of origin/devel. Grrr. No harm done, I
think, because these changes were the ones that start to add asciidoc
rendering, and they work on my computer at least. They don't change any
On Thu, Aug 20, 2020 at 5:05 PM Edward K. Ream wrote:
> This is an experimental restriction. It can easily be removed.
>
> I think requiring PR's for devel and master makes sense. They alert
> everyone of proposed changes before they take effect. The PR's themselves
> are a permanent record of
31 matches
Mail list logo
