TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: T.Willey on January 17, 2013, 04:33:01 PM
-
I did not see any repercussions for this error with my lisp that I just wrote, but was wondering if anyone else has seen this? Seems to happen every time.
Command: (getstring)
(
Can't reenter LISP.
"("
-
Not sure I fully understand what you mean, Tim... So, FWIW -
(
Can't reenter LISP.
"("
(this is a test)
Can't reenter LISP.
"(this is a test)"
-
I haven't tested any .NET code myself, but perhaps this is an issue where one is attempting to type LISP within Editor.GetString() ? :? *not sure*
-
AutoCAD 2013:
Command: (getstring)
(
Can't reenter LISP.
"("
Command: (getstring t)
(
"("
-
The issue was when entering an open parenthesis to 'getstring', the error "Can't reenter Lisp." would show up, but not stop the Lisp routine running. I was just wondering if anyone has ever seen this issue, and if has caused some errors in the long run?
That solution worked for me in '12 also Lee. Thanks for that. Never crossed my mind, in my rush to code my simple routine that I needed.
-
The issue was when entering an open parenthesis to 'getstring', the error "Can't reenter Lisp." would show up, but not stop the Lisp routine running. I was just wondering if anyone has ever seen this issue, and if has caused some errors in the long run?
That solution worked for me in '12 also Lee. Thanks for that. Never crossed my mind, in my rush to code my simple routine that I needed.
No worries Tim; I'm surprised I've never noticed/encountered this result before :|
-
+1 for the thread title.
-
Wow! Does seem irritating doesn't it? I also can't remember this happening. Must be some new "adesk-derived-feature" :ugly:
-
+1 for the thread title.
+1 more (LOL)
(defun c: grammercheck ()
-
+1 for the thread title.
+1 more (LOL)
(defun c: grammercheck ()
(http://images.wikia.com/uncyclopedia/images/5/55/Knuth_don_has_a_grammar.jpg)
-
+1 for the thread title.
+1 more (LOL)
(defun c: grammercheck ()
:lmao:
Thanks for pointing that out Lee, I would like to say that I did that on purpose but... :-[
-
What is TEXTEVAL sysvar set to? -David
-
+1 for the thread title.
I thought this was a spinoff of the Snapchat thread. ^-^
-
What is TEXTEVAL sysvar set to? -David
Good suggestion David, but after a quick test on my system it seems that the TEXTEVAL System Variable unfortunately has no effect on this behaviour of the getstring function. :-(
-
Looks like this is the case all the way to alt least R12 DOS. From the customization guide:
The user cannot enter another AutoLISP expression as the response a getstring request.
-David
-
but what if the respondent desires to enter something in parenthesis ... something that is not for lisp evaluation?
-
but what if the respondent desires to enter something in parenthesis ... something that is not for lisp evaluation?
To clarify, its still possible to enter a string starting with an open parenthesis at the getstring prompt, and the getstring function will still return this entered string correctly, however, you just receive the annoying Can't reenter LISP message to accompany it:
Command: (getstring "\nEnter String: ")
Enter String: (test)
Can't reenter LISP.
"(test)"
-
hmm .. nomutt perhaps?
-
Tried, doesn't help. Neither does CmdEcho.