Many thanks
---eric
--
Speech-recognition in use. It makes mistakes, I correct some.
maybe I've been living with Emacs are way too many years (20 at last count) but
the indent/outdent process doesn't seem quite right to me.
def xyz():
z=1
def asd():^
if you hit the tab key at the ^ it doesn't change the indentation of the line.
even if you add a return on the previous function, indent or outdent don't work
properly. In order to change the indentation, first and need to navigate to
start of the line (as opposed to beginning of line) then emit the outdent or
indent key sequence.
another problem shows up when you put your cursor on the start of the line z=1
and hit the tab key. As you would expect, it indents four spaces. Then if you
hit the backspace key, it outdents to the beginning of the line.
curious.
maybe I've been living with Emacs are way too many years (20 at last count) but
the indent/outdent process doesn't seem quite right to me.
def xyz():
z=1
def asd():^
In order to change the indentation, first and need to navigate to
start of the line (as opposed to beginning of line) then emit the outdent or
indent key sequence.
another problem shows up when you put your cursor on the start of the line z=1
and hit the tab key. As you would expect, it indents four spaces. Then if you
hit the backspace key, it outdents to the beginning of the line.
and I guess you excuse people driving on the left as how they do it in England
and other places. :-)
> another problem shows up when you put your cursor on the start of
> the line z=1
> and hit the tab key. As you would expect, it indents four
> spaces. Then if you
> hit the backspace key, it outdents to the beginning of the line.
>
>
> This is due to the "Smart Tab delete" option, which aligns the line with
> the line above. You could use Shift-Tab instead of Backspace.
oh I see. That's really nonintuitive. yes, I am thoroughly aware that the only
truly intuitive user interface is the mammalian nipple and even then, there are
those that still can't grasp the concept.
by the way, I found an interesting bug in indentation. turn on show all
invisible characters (spaces, new lines etc.) Create a class definition. hit
return. You should now see the cursor sitting at the end of four spaces and a
paragraph symbol. Backspace. This should put you up against the left-hand
margin. Hit the tab key. The paragraph symbol stays at the left-hand margin
and the cursor moves over six spaces.
I should have told you that I'm one of those people that breaks anything I touch...
;-)
like this?
class tpblue_store(file_store.store):
123
cache_factory= tpblue_cache
meta_attribute = meta_storage.meta_names.keys()
I typed 123 and yes, the paragraph symbol moves to the end of line but I still
have six spaces in front. Remember, as I reported, if you hit return,
backspace, and then the tab key after a class definition, you will get six
spaces at the start of a line. The only place it seems to happen is right after
a class definition. if you aren't able to reproduce it, I will try to find
other places where the failure occurs and give a few more examples.
---eric
another bit of nonintuitive behavior. an actual code fragment. What would you
expect if you went to the start of the "if" and typed the backspace key or shift
tab key? my expectation is it would outdent by four spaces.
# strip off last comma
meta_dictionary[i] = accrue_value[:-1]
elif i == 'mini-body':
What it does is outdent to the start of the line as shown below.
# strip off last comma
meta_dictionary[i] = accrue_value[:-1]
elif i == 'mini-body':
One last note for the evening. It's been rather frustrating pyscripter. Many
features that you have are quite useful if you can type. If you use speech
recognition many bugs in the "plain text dictation to any application" mode
(a.k.a. natural text in NaturallySpeaking), you end up typing almost as much
correcting misrecognition errors as you do just typing.
There's nothing you can do about it. I'm just stuck until nuance fixes bugs
that are close to seven years old.