Hey,
I'm new at Textmate, so maybe it's not a bug but a problem between the chair and the computer :-) I'm trying to implement the comment reflow thingy that I just saw on the screencasts, and for some reason the input is receiving the whole document instead of the text at scope.
You can view a screenshot of the command here: http://img228.imageshack.us/img228/7031/reflowcommandil4.png Unexpected result: http://img228.imageshack.us/img228/2390/unexpectedoutputnz3.png Current scope: http://img136.imageshack.us/img136/2240/currentscopejw2.png
Can you give me any help? Thanks
Cumprimentos, António Afonso
On 8 Dec 2008, at 13:19, António Afonso wrote:
I'm new at Textmate, so maybe it's not a bug but a problem between the chair and the computer :-) I'm trying to implement the comment reflow thingy that I just saw on the screencasts, and for some reason the input is receiving the whole document instead of the text at scope. [...] Can you give me any help?
Not sure what could be wrong. Did you close the bundle editor after changing the scope selector? Try maybe relaunch TM and also try ⌃Q outside the comment block to see if the command is properly scoped.
On 8 Dec 2008, at 13:19, António Afonso wrote:
I'm new at Textmate, so maybe it's not a bug but a problem between the chair and the computer :-) I'm trying to implement the comment reflow thingy that I just saw on the screencasts, and for some reason the input is receiving the whole document instead of the text at scope. [...] Can you give me any help?
Not sure what could be wrong. Did you close the bundle editor after changing the scope selector? Try maybe relaunch TM and also try ?Q outside the comment block to see if the command is properly scoped.
I've had this problem with newly created commands for as long as I can remember. The solution is to restart TextMate. The problem only exists with newly created commands.
Joachim Mårtensson
Not sure what could be wrong. Did you close the bundle editor after changing the scope selector? Try maybe relaunch TM and also try ?Q outside the comment block to see if the command is properly scoped.
I've had this problem with newly created commands for as long as I can remember. The solution is to restart TextMate. The problem only exists with newly created commands.
It's now working, thank you very much, both of you.
Cumprimentos, António Afonso
-
Allan Odgaard -
António Afonso -
Joachim Mårtensson