Branching and commands

[Anderson Santos]

Hello everyone

Sorry for the silly question, but I am not used to launchpad and bazaar, just to github, so I'm not sure if I did it right.

I created a local branch from lp:enso and then I pushed to my new linux-improvements branch in Launchpad. Is it the correct way of doing it? I had to use --use-existing-dir to do that, so I was not sure if it's correct.

Second, I really don't know what's the correct way of registering a command. I did some tricks creating an ensocommands file on my home dir and executing external files to have many commands installed but I thought it should be easier. And when downloading the command from the ensohub nothing happens, maybe the lp:enso does not implemented the web install yet or maybe it's a problem with my installation?

Any help will be appreciate

Cheers

Anderson

--
anderson@anderson-desktop:~$ cowsay £\> Love me, choose vegan \<3

 _____________________________
< £> Love me, choose vegan <3 >
 -----------------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

anderson.santos.br@gmail.com
www.andersonsantos.info

[blackdaemon]

Hi Andreson,

the process of working on branches is described here:
http://groups.google.com/group/enso-developers/msg/7ead09b0b863347e
You have created the local branch correctly. You should not need the --
use-existing-dir parameter
as far as you invoke the 'bzr branch' command in your main development
directory, whatever it is.
Subdirectory with the branch name will be created automatically.

There should be no special magic around registering new commands.
Either you put them
into ~/.ensocommands file, or you create new python file in the
commands directory
(this is typically ~/enso/commands).
Should the file contain the valid command definition, it will register
it automatically at
next quasimode open. Valid command definition is (must begin with
"cmd_"):

def cmd_some_command(ensoapi):
...
def cmd_some_command_with_param(ensoapi, param = None):
...
def cmd_some_command_with_param_list(ensoapi, param = None):
...
cmd_some_command_with_param_list.valid_args = ['param1', 'param2']

This is described in detail in the following link:
http://code.google.com/p/enso/

As the web install is not working for you and commands are not
recognized,
it looks like Enso has problem determining the correct path to the
scripts directory.
If you are on Linux, my guess is that you have missing dependency:
python-xdg
as xdg.BaseDirectory class is used to get the info. See here:

http://bazaar.launchpad.net/~anderson-santos-br/enso/linux-improvements/annotate/head:/enso/platform/linux/scriptfolder.py

Are you getting any errors in the Enso log?


On Jul 15, 3:50 pm, Anderson Santos <anderson.santos...@gmail.com>
wrote:

> anderson.santos...@gmail.comwww.andersonsantos.info