Re: IDL Workbench Nits [message #57972] |
Thu, 10 January 2008 12:57  |
Bob[3]
Messages: 60 Registered: December 2006
|
Member |
|
|
On Jan 10, 3:43 pm, Abraham campbell <abra...@ittvis.com> wrote:
> There is a difference between multi-line paste and single-line paste.
> When you paste multiple lines into the command line window, it
> immediately executes each line, one at a time, without displaying the
> lines in the command line, and without you being able to modify the
> command before it's executed. (NOTE: The last line of a multi-line
> paste is also executed immediately.) However, with a single-line paste,
> the command is left in the command line window, and not immediately
> executed, so that you can modify it before executing it.
>
> What you might be running into is the case where you have a single
> statement, but you have also copied a newline character at the end of
> the statement. When you paste this into the command line, it will
> behave like a multi-line paste and immediately execute the (single)
> command and not give you a chance to edit the command before execution.
>
> The presence of a carriage return/newline character anywhere in the
> pasted text determines the difference between multi-line and single-line
> paste behavior.
>
> Abraham- Hide quoted text -
>
> - Show quoted text -
If that is the case, then the copy/paste behaviour could be made more
intuitive/consistent if when there is only one carriage return/newline
character in the text (ie it's a single-line paste that just happens
to have a newline at the end) it gets stripped off before pasting.
Bob.
|
|
|
Re: IDL Workbench Nits [message #57975 is a reply to message #57972] |
Thu, 10 January 2008 12:43   |
Abraham campbell
Messages: 10 Registered: January 2008
|
Junior Member |
|
|
David Fanning wrote:
> David Fanning writes:
>
>> Ah, here is this problem in a reproducible form.
>>
>> I read an interesting article on the IDL newsgroup
>> (probably not one of my own). I want to check it out.
>> So I cut a line of code from the newsgroup article,
>> and try to paste it into my Command Window. It goes
>> *directly* into the Console Window, and it gets
>> executed immediately. But, it never shows up in the Command
>> Line window.
>
> Well, maybe this is normal. Not a good example, in
> any case. I'll have to keep looking. Something is
> weird here, but I can't put my finger on it at the
> moment.
>
> Cheers,
>
> David
There is a difference between multi-line paste and single-line paste.
When you paste multiple lines into the command line window, it
immediately executes each line, one at a time, without displaying the
lines in the command line, and without you being able to modify the
command before it's executed. (NOTE: The last line of a multi-line
paste is also executed immediately.) However, with a single-line paste,
the command is left in the command line window, and not immediately
executed, so that you can modify it before executing it.
What you might be running into is the case where you have a single
statement, but you have also copied a newline character at the end of
the statement. When you paste this into the command line, it will
behave like a multi-line paste and immediately execute the (single)
command and not give you a chance to edit the command before execution.
The presence of a carriage return/newline character anywhere in the
pasted text determines the difference between multi-line and single-line
paste behavior.
Abraham
|
|
|
Re: IDL Workbench Nits [message #57982 is a reply to message #57975] |
Thu, 10 January 2008 09:25   |
Doug Edmundson
Messages: 58 Registered: November 2005
|
Member |
|
|
David Fanning wrote:
> Folks,
>
> I'm not sure if this is a question or a report. But a couple of
> things I've discovered:
>
> 1. I'm writing a file with a rather long filename. When I get
> finished with it, I compile it, and go down to the command
> line to run it. I type the first couple of letters of its
> name, then hit CNTL-space. I see a list of the modules in the
> file. I choose the appropriate one. The name of the program
> is completed on the command line. Now I hit the CR.
>
> Nothing. The "command" disappears. But nothing appears
> in the Console View, and my program doesn't run. The command
> doesn't show up in my command history. Is this a bug?
>
> 2. In Windows IDLDE in 6.4, if I put a breakpoint in a file
> and run the file, I hit the breakpoint and I can step through
> the file. Typically, I discover the thing I was trying to find,
> make a couple of changes in the file, hit the Save and Compile
> icon, hit the remove all breakpoints button, and off I go again.
>
> In the IDL Workbench, my file pointer, even after I recompile
> the file, is still inside the file. I can't do much of anything
> until I remember I have to type RETALL. I last typed RETALL this
> much back in the 1960s. Is this possibly a bug? I really prefer
> when I re-compile that my file pointer be removed from the file.
>
> Oh, wait a minute. Maybe this is a problem with the file pointer
> not being updated correctly. I think the recompile actually
> removes the file pointer, but I don't get visual confirmation
> of that fact. (I think we talked about this before and agreed
> it was a bug, now that I think about it.) Anyway, RETALL
> refreshes the file enough to remove the file pointer in the file.
>
> Cheers,
>
> David
Regarding (1), we've seen this too and have been looking into it. I
think we're close to a fix on the "ctrl+space" issue and are looking at
command recall issues.
You're right about (2) being a bug. Doing something like "print, 1 + 0"
at the command line should force a refresh of the Eclipse debug model
and remove the erroneous instruction pointer. Though being really
confusing, it is more of a visual thing, so it shouldn't affect how IDL
runs. Underneath all that UI, the state of IDL is correct.
Cheers,
Doug
|
|
|
Re: IDL Workbench Nits [message #57983 is a reply to message #57982] |
Thu, 10 January 2008 09:09   |
Doug Edmundson
Messages: 58 Registered: November 2005
|
Member |
|
|
Ryan. wrote:
>> Like you, I have seen this only happen occasionally, and I
>> haven't been able to pinpoint the exact circumstances, but
>> it seems to me that when I am using my arrow keys to recall
>> commands, that the command is executed immediately upon
>> recall. What I want, of course, is to recall a command
>> to the command line so I can make a change to it, not to
>> execute it right away. I don't want it to execute until I
>> have hit the Carriage Return. When the command sets of a long program,
>> this is MOST annoying.
>
> I haven't experienced that.....yet. The command line seems to work as
> it should for me. But I can only imagine how annoying it can be.
>
> One thing I just noticed is that if you have a string with this slash
> "\" in it, the variables prints it as having two.
>
> Here is a sample:
> IDL> sasfname = 'Z:\test\sas\SAS_WEEK49.SAS'
> IDL> print, sasfname
> Z:\test\sas\SAS_WEEK49.SAS
>
> but in the Variables Window it says:
> Z:\\test\\sas\\SAS_WEEK49.SAS
>
> But it doesn't work the same way if you use the other slash:
> IDL> sasfname_otherslash = 'Z:/test/sas/SAS_WEEK49.SAS'
> IDL> print, sasfname_otherslash
> Z:/test/sas/SAS_WEEK49.SAS
>
> and in the Variables window it says:
> Z:/test/sas/SAS_WEEK49.SAS
>
>
> This might be how Eclipse works but can be misleading if I use the
> Variables window often.
>
> Ryan.
Hi Ryan,
Just a quick update... the bug with backslashes in the variables view
has been logged. Thanks for the report.
Cheers,
Doug
|
|
|
Re: IDL Workbench Nits [message #57987 is a reply to message #57983] |
Thu, 10 January 2008 08:19   |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> Ah, here is this problem in a reproducible form.
>
> I read an interesting article on the IDL newsgroup
> (probably not one of my own). I want to check it out.
> So I cut a line of code from the newsgroup article,
> and try to paste it into my Command Window. It goes
> *directly* into the Console Window, and it gets
> executed immediately. But, it never shows up in the Command
> Line window.
Well, maybe this is normal. Not a good example, in
any case. I'll have to keep looking. Something is
weird here, but I can't put my finger on it at the
moment.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
Re: IDL Workbench Nits [message #57988 is a reply to message #57987] |
Thu, 10 January 2008 08:11   |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> Like you, I have seen this only happen occasionally, and I
> haven't been able to pinpoint the exact circumstances, but
> it seems to me that when I am using my arrow keys to recall
> commands, that the command is executed immediately upon
> recall. What I want, of course, is to recall a command
> to the command line so I can make a change to it, not to
> execute it right away. I don't want it to execute until I
> have hit the Carriage Return. When the command sets of a long
> program, this is MOST annoying.
Ah, here is this problem in a reproducible form.
I read an interesting article on the IDL newsgroup
(probably not one of my own). I want to check it out.
So I cut a line of code from the newsgroup article,
and try to paste it into my Command Window. It goes
*directly* into the Console Window, and it gets
executed immediately. But, it never shows up in the Command
Line window.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
Re: IDL Workbench Nits [message #57991 is a reply to message #57988] |
Thu, 10 January 2008 07:43   |
Ryan.
Messages: 77 Registered: March 2006
|
Member |
|
|
> Like you, I have seen this only happen occasionally, and I
> haven't been able to pinpoint the exact circumstances, but
> it seems to me that when I am using my arrow keys to recall
> commands, that the command is executed immediately upon
> recall. What I want, of course, is to recall a command
> to the command line so I can make a change to it, not to
> execute it right away. I don't want it to execute until I
> have hit the Carriage Return. When the command sets of a long
> program, this is MOST annoying.
I haven't experienced that.....yet. The command line seems to work as
it should for me. But I can only imagine how annoying it can be.
One thing I just noticed is that if you have a string with this slash
"\" in it, the variables prints it as having two.
Here is a sample:
IDL> sasfname = 'Z:\test\sas\SAS_WEEK49.SAS'
IDL> print, sasfname
Z:\test\sas\SAS_WEEK49.SAS
but in the Variables Window it says:
Z:\\test\\sas\\SAS_WEEK49.SAS
But it doesn't work the same way if you use the other slash:
IDL> sasfname_otherslash = 'Z:/test/sas/SAS_WEEK49.SAS'
IDL> print, sasfname_otherslash
Z:/test/sas/SAS_WEEK49.SAS
and in the Variables window it says:
Z:/test/sas/SAS_WEEK49.SAS
This might be how Eclipse works but can be misleading if I use the
Variables window often.
Ryan.
|
|
|
Re: IDL Workbench Nits [message #57992 is a reply to message #57991] |
Thu, 10 January 2008 06:27   |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
Ryan. writes:
> I've noticed this too. It doesn't necessarily happen with long file
> names though. I sometimes put in "junk = 1" to test and nothing happens
> when I notice this peculiar behavior. It only happens on occasion but I
> haven't yet figured out what triggers it.
This reminds me of another thing I've noticed.
Like you, I have seen this only happen occasionally, and I
haven't been able to pinpoint the exact circumstances, but
it seems to me that when I am using my arrow keys to recall
commands, that the command is executed immediately upon
recall. What I want, of course, is to recall a command
to the command line so I can make a change to it, not to
execute it right away. I don't want it to execute until I
have hit the Carriage Return. When the command sets of a long
program, this is MOST annoying.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
Re: IDL Workbench Nits [message #58071 is a reply to message #57972] |
Thu, 10 January 2008 13:45  |
Paul Van Delst[1]
Messages: 1157 Registered: April 2002
|
Senior Member |
|
|
Bob Crawford wrote:
> On Jan 10, 3:43 pm, Abraham campbell <abra...@ittvis.com> wrote:
>> There is a difference between multi-line paste and single-line paste.
>> When you paste multiple lines into the command line window, it
>> immediately executes each line, one at a time, without displaying the
>> lines in the command line, and without you being able to modify the
>> command before it's executed. (NOTE: The last line of a multi-line
>> paste is also executed immediately.) However, with a single-line paste,
>> the command is left in the command line window, and not immediately
>> executed, so that you can modify it before executing it.
>>
>> What you might be running into is the case where you have a single
>> statement, but you have also copied a newline character at the end of
>> the statement. When you paste this into the command line, it will
>> behave like a multi-line paste and immediately execute the (single)
>> command and not give you a chance to edit the command before execution.
>>
>> The presence of a carriage return/newline character anywhere in the
>> pasted text determines the difference between multi-line and single-line
>> paste behavior.
>>
>> Abraham- Hide quoted text -
>>
>> - Show quoted text -
>
> If that is the case, then the copy/paste behaviour could be made more
> intuitive/consistent if when there is only one carriage return/newline
> character in the text (ie it's a single-line paste that just happens
> to have a newline at the end) it gets stripped off before pasting.
I don't see how that follows. Sometimes I copy/paste single lines and I want the newline
included. Other times I don't. It depends.
All the c.l.i-p ng traffic about the Workbench would seem to indicate that letting the
application make the choices behind-the-scenes is just bad mojo of the 10ft pole variety.
Then again, maybe it's because eclipse was created by and for the software industry. IDL
users have a goodly number of scientists in their ranks. Maybe the thought processes of
the two groups are just too antipodal.
?
cheers,
paulv
|
|
|