RE: default indents
I've seen this happen before LispWorks has expanded a new macro. In other
words, if I write a new macro, then use it somewhere, I'll get the
indentation you describe. However, if I write a new macro, compile it,
*then* use it somewhere, indentation is as expected.
Cheers,
David E. Young
Bloodhound Software, Inc.
http://bloodhoundinc.com
"For wisdom is more precious than rubies,
and nothing you desire can compare with her."
-- Proverbs 8:11
"But all the world understands my language."
-- Franz Joseph Haydn (1732-1809)
-----Original Message-----
From: John DeSoi [mailto:jd@icx.net]
Sent: Thursday, July 10, 2003 10:35 AM
To: lisp-hug@xanalys.com
Subject: default indents
I'm stumped as to why the default indentation of macros is arbitrarily
different. For example:
(let-connection ()
(test 1234))
(let-connection2 ()
(test 134))
I can fix let-connection2 by adding an entry in my init file for
editor:setup-indent, but I hate to do that every time I create a macro.
Is there some way to globally specify this?
Thanks,
John DeSoi, Ph.D.
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
Re: default indents
On Thursday, July 10, 2003, at 10:50 AM, Young, David wrote:
> I've seen this happen before LispWorks has expanded a new macro. In
> other
> words, if I write a new macro, then use it somewhere, I'll get the
> indentation you describe. However, if I write a new macro, compile it,
> *then* use it somewhere, indentation is as expected.
>
Yes, that was it -- indents differently if the macro is evaluated
versus compiled.
Which brings up the next question. I sometimes evaluate things because
I find it distracting that compiling always switches to the Output tab.
Unless there is an error or warning, evaluating stays in on in the Text
view and puts a "Finished Evaluating" message at the bottom of the
window. Is there a way to make compiling work the same way - only
switch to Output if there is an error or warning?
Thanks,
John DeSoi, Ph.D.
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________