Custom Query (1030 matches)

Double clicking to the left of an open paren, highlights the following s-expression and double clicking to the right of a close paren, highlights the previous s-expression. Very useful. Double clicking next to double quotes should behave the same way for strings.

I'm looking for a way to find the boundaries of a string. It might be a good idea to make double quotes blink like parens. While we're at it, let's make other delimiters blink too. I can think of square brackets, curly braces, #| and |#.

I suggest that quotes should not be required when typing the directory name for the toplevel 'cd' command.

I am evaluating Clozure CL on x86 Windows. My 1st experience of it was trying to change my working directory so that I could load a lisp file. I typed :? and got some help. PWD worked as per the help given. CD DIR seemingly did not. Whatever I typed, I got errors. Didn't matter if it was cd C:/blah, :cd C:/blah, or :cd \blah. I started to think that the Clozure port on Windows might not be very reliable, since I had read it was relatively recent.

I pulled the latest Clozure version from SVN just in case this was a bug that had been fixed. I searched the bug tracker for entries. Only then did I notice that all examples were given as cd "X:/some/dirname" with quotes around the directory name. This is counter to typical command shell usage. I did figure out the necessity of the colon : escape mechanism; I don't begrudge that. But if I'm going to type a colon : escape, why should I have to type any more extra mumbo jumbo to get the command to behave like a shell command?

If it is not feasible to remove the quoting requirement, the :? HELP should at least say CD "DIR" and give an example, so that a new user knows that they have to type quotes around the directory name.