For anyone using the pytest framework I've written a button which jumps
between code and corresponding test, creating missing folders / files /
functions as needed. It's doc'ed in it's doc string.
https://github.com/leo-editor/snippets/blob/master/utils/pytest_switch.py
Cheers -Terry
--
You
On Tue, 27 Feb 2018 14:36:08 -0600
"Edward K. Ream" wrote:
> On Tue, Feb 27, 2018 at 2:19 PM, Matt Wilkie wrote:
>
> Would it be easier to invert the process, and have dedicated releases
> > branches and then master never needs to be frozen?
>
>
> Adding branch.md to .gitignore would allow branch devs to document their
> branch-specific work, without the possibility of overwriting this file when
> merging (in either direction).
>
name-of-branch.md ?
--
You received this message because you are subscribed to the Google Groups
> BUT:
> Leo can not like IDE/Jupyter can running on the spot,
> and every one time change interface,
> such as leave Leo, jump into iTerm2 for running code , observe log
> printing,
> will hurt attention, lost Mind Cache...
>
+1. This is why I tend to use Pyzo when prototyping new
>
> It has been almost 14 months since I discovered Leo and today I recalled
> how I found it.
>
Thanks for this thread. I've been trying to recall my own path of
discovery. No concrete memory has emerged, but it was somewhere in the
intersection of being dissatisfied with wiki notes and
On Tue, Feb 27, 2018 at 2:19 PM, Matt Wilkie wrote:
Would it be easier to invert the process, and have dedicated releases
> branches and then master never needs to be frozen?
>
Anything is possible, but I don't see how doing all the work outside of
master is any improvement.
Yay!!
--
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...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
> Please hold commits into master for just a bit longer.
>>
>
> I have just deleted the 5.8-dev branch. The master branch is now open.
>
> Feel free to create branches as needed for your own projects.
>
Would it be easier to invert the process, and have dedicated releases
branches and then
Hi Kevin,
No problem.
It works like this because of how Leo loads settings. A settings tree in
the file itself is valid, so reading all of the settings when loading the
file makes sense.
Chris
On Tue, Feb 27, 2018 at 11:32 AM, k-hen wrote:
> Thanks Chris, much
Thanks Chris, much appreciated.
I was hoping that it could take immediate effect somehow,
but reloading just the file(s) is definitely easier than the whole
application.
Kevin
On Tuesday, February 27, 2018 at 2:35:33 PM UTC-3:30, Chris George wrote:
>
> Hi Kevin,
>
> Welcome.
>
> All you
Hi Kevin,
Welcome.
All you need to do is:
1) Make the change to the setting.
2) Save the settings file.
3) Run reload-settings or "Reload-Settings" from the "Settings"
menu.
4) Close the file.
5) Reopen the file to see your new settings take effect.
Chris
On Tue, Feb 27, 2018 at 9:47 AM,
Hi All,
I'm happy and excited to be ramping up in Leo, but like many I'm sure, am
having some minor pains getting up to speed.
I'm making edits to my 'myLeoSettings.leo' file and would like to know what
the fast way of re-applying those settings is.
I figured that the 'Reload-Settings' feature
On Tuesday, February 27, 2018 at 11:02:02 AM UTC-6, Edward K. Ream wrote:
Please hold commits into master for just a bit longer.
>
I have just deleted the 5.8-dev branch. The master branch is now open.
Feel free to create branches as needed for your own projects.
Edward
--
You received this
The 5.8-dev branch has been merged into master and will be deleted soon.
The version in master is now 5.8-devel.
The master branch contains Terry's great new match-brackets code.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To
Please hold commits into master for just a bit longer.
Edward
--
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...@googlegroups.com.
To post to
On Tue, Feb 27, 2018 at 8:44 AM, vitalije wrote:
> I am not 100% sure, but I believe those values are actually tree fragments
> represented in xml.
>
Exactly. They should be filtered out, perhaps replaced with a message to
that effect.
Edward
--
You received this
On Tue, Feb 27, 2018 at 8:51 AM, Terry Brown wrote:
> On Tue, 27 Feb 2018 08:33:10 -0600
> Kent Tenney wrote:
>
> > In the midst of the settings, I see a bunch of text from Leo files:
>
> In leoSettings.leo or myLeoSettings.leo?
Kent means in the
On Tue, 27 Feb 2018 08:33:10 -0600
Kent Tenney wrote:
> In the midst of the settings, I see a bunch of text from Leo files:
In leoSettings.leo or myLeoSettings.leo? I've seen that sort of thing
happen when you drag and drop a node into body text or maybe copy a
node and
On Tue, Feb 27, 2018 at 8:33 AM, Kent Tenney wrote:
> In the midst of the settings, I see a bunch of text from Leo files:
>
These are from tree-*valued* abbreviations.
I have just created #748: Skip tree-valued settings in print-settings
command
I am not 100% sure, but I believe those values are actually tree fragments
represented in xml.
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 it, send an email
to
In the midst of the settings, I see a bunch of text from Leo files:
...
searchbody = True
searchheadline = True
sectionnamecolor = red
selectalltextwheneditingheadlines = False
selectedtabbg = @LightSteelBlue1
settingsfindermenu =
21 matches
Mail list logo