I've just added this to the action-items list, which means they are
likely to be fixed first.
Thank you Edward. There was a question in this thread that I still
need an answer, so I will repeat it again.
I can't figure how to change color of ( and ) in
actionscript language. I like dark
On May 18, 3:16 pm, Ville M. Vainio vivai...@gmail.com wrote:
Scanning through the to-do list just now, I came across an old item
requesting versioning of nodes. I'd like to do that before the next
release, be it a1 or b1.
Are you sure? There are several ways to do this, none of which
On Thu, May 19, 2011 at 6:48 AM, Edward K. Ream edream...@gmail.com wrote:
2. The simplest thing that could possibly work is extremely simple:
just add an undo stack and stack pointer to every vnode.
The undo code will do this only as necessary using hasattr and
setattr. Thus, the changes
On Thu, May 19, 2011 at 2:48 PM, Edward K. Ream edream...@gmail.com wrote:
On May 18, 3:16 pm, Ville M. Vainio vivai...@gmail.com wrote:
2. The simplest thing that could possibly work is extremely simple:
just add an undo stack and stack pointer to every vnode. This will
Ah, you were talking
On Thu, May 19, 2011 at 7:12 AM, Ville M. Vainio vivai...@gmail.com wrote:
Ah, you were talking about per-node UNDO, not versioning.
Never mind that, you are right, there is obvious way to do it.
Glad you agree. I'm working on it now.
After a false start it looks like there is a way to do
On Thu, May 19, 2011 at 8:33 AM, Kent Tenney kten...@gmail.com wrote:
To browse back in forth in time in a node would be
extremely useful and powerful, a huge productivity boost.
That may be, but it is not likely to happen for 4.9.
Edward
--
You received this message because you are
Looks good.
Do you also have any bzr specific gotchas that you plan to add to this
section?
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send
On Thu, May 19, 2011 at 9:33 AM, Kent Tenney kten...@gmail.com wrote:
So versioning remains an elusive feature.
To browse back in forth in time in a node would be
extremely useful and powerful, a huge productivity boost.
Given my workflow, much more useful than regular file based
version
On Thu, May 19, 2011 at 9:51 AM, Ville M. Vainio vivai...@gmail.com wrote:
On Thu, May 19, 2011 at 9:33 AM, Kent Tenney kten...@gmail.com wrote:
So versioning remains an elusive feature.
To browse back in forth in time in a node would be
extremely useful and powerful, a huge productivity
I'm at Hyatt regency, California for the next week. (MeeGo
Conference). If any one is living in the nearby, perhaps we could talk
about some long term visions for leo, or whatever
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this
On Thu, 19 May 2011 15:40:12 -0400
Ville M. Vainio vivai...@gmail.com
wrote:
I'm at Hyatt regency, California for the next week. (MeeGo
Conference). If any one is living in the nearby, perhaps we could talk
about some long term visions for leo, or whatever
The best thing you can do is to
On Thu, May 19, 2011 at 8:09 AM, Edward K. Ream edream...@gmail.com wrote:
It looks like there is a way to do it without changing any existing code in
leoUndo.py.
Rev 4085 contains what *might* be considered working code. Please
read on for details and warnings.
At present the new code is
On Thu, May 19, 2011 at 9:45 AM, zpcspm zpc...@gmail.com wrote:
Do you also have any bzr specific gotchas that you plan to add to this
section?
I use the following batch files related to bzr:
b: short for bzr
bs: short for bzr status
tr: short for cd path to trunk
main: short for cd path to
13 matches
Mail list logo
