I can't imagine that no-one else has seen this problem. Assume you have package name like foo.bar, if I see the prompt I expect to see the package name. but I just got bar>
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
Regards Friedrich
On Tue, 09 Aug 2005 14:46:32 +0200, Friedrich Dominicus frido@q-software-solutions.de wrote:
I can't imagine that no-one else has seen this problem. Assume you have package name like foo.bar, if I see the prompt I expect to see the package name. but I just got bar>
You're most likely seeing a nickname you've defined yourself (or the author of the library you're using).
From swank.lisp:
(defun package-string-for-prompt (package) "Return the shortest nickname (or canonical name) of PACKAGE."
Cheers, Edi.
Friedrich Dominicus frido@q-software-solutions.de writes:
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
this behaviour is controlled by the swank:*auto-abbreviate-dotted-packages* variable, set it to NIL in your .swank.lisp to avoid this behaviour. You will still get the 'shortest-package-nickname' though (i don't see a variable to disable even that).
hth.
"Marco Baringer" mb@bese.it writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
this behaviour is controlled by the swank:*auto-abbreviate-dotted-packages* variable, set it to NIL in your .swank.lisp to avoid this behaviour. You will still get the 'shortest-package-nickname' though (i don't see a variable to disable even that).
thanks for the hint. I did not expect special treatment for that I did not even had an idea to look after that.
Regards Friedrich
Friedrich Dominicus frido@q-software-solutions.de writes:
"Marco Baringer" mb@bese.it writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
this behaviour is controlled by the swank:*auto-abbreviate-dotted-packages* variable, set it to NIL in your .swank.lisp to avoid this behaviour. You will still get the 'shortest-package-nickname' though (i don't see a variable to disable even that).
thanks for the hint. I did not expect special treatment for that I did not even had an idea to look after that.
FWIW, I put in that feature because I believe in using long, domain qualified package names (a la Java packages) which means that my package names are always prefaced with essentially noise. I'd much rather see:
FOO>
than:
COM.GIGAMONKEYS.FOO>
when *all* my package names start with COM.GIGAMONKEYS. But the flag is there to turn it off if you don't like (which you probably won't if you use short package names that happen to contain a dot.)
-Peter
Peter Seibel writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
"Marco Baringer" mb@bese.it writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
this behaviour is controlled by the swank:*auto-abbreviate-dotted-packages* variable, set it to NIL in your .swank.lisp to avoid this behaviour. You will still get the 'shortest-package-nickname' though (i don't see a variable to disable even that).
thanks for the hint. I did not expect special treatment for that I did not even had an idea to look after that.
FWIW, I put in that feature because I believe in using long, domain qualified package names (a la Java packages) which means that my package names are always prefaced with essentially noise. I'd much rather see:
FOO>
than:
COM.GIGAMONKEYS.FOO>
when *all* my package names start with COM.GIGAMONKEYS. But the flag is there to turn it off if you don't like (which you probably won't if you use short package names that happen to contain a dot.)
The algorithm should check for the presence of several packages with the same last part, and use more parts in these cases.
COM.GIGAMONKEYS.FOO ---> GIGAMONKEYS.FOO COM.INFORMATIMAGO.FOO INFORMATIMAGO.FOO
UK.CO.SMART-SOFT.FOO ---> UK.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO
On Aug 10, 2005, at 3:34 AM, Pascal Bourguignon wrote:
Peter Seibel writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
"Marco Baringer" mb@bese.it writes:
Friedrich Dominicus frido@q-software-solutions.de writes:
Is that on purpose? Is it a bug, is something wrong with a foo.bar name?
this behaviour is controlled by the swank:*auto-abbreviate-dotted-packages* variable, set it to NIL in your .swank.lisp to avoid this behaviour. You will still get the 'shortest-package-nickname' though (i don't see a variable to disable even that).
thanks for the hint. I did not expect special treatment for that I did not even had an idea to look after that.
FWIW, I put in that feature because I believe in using long, domain qualified package names (a la Java packages) which means that my package names are always prefaced with essentially noise. I'd much rather see:
FOO>
than:
COM.GIGAMONKEYS.FOO>
when *all* my package names start with COM.GIGAMONKEYS. But the flag is there to turn it off if you don't like (which you probably won't if you use short package names that happen to contain a dot.)
The algorithm should check for the presence of several packages with the same last part, and use more parts in these cases.
COM.GIGAMONKEYS.FOO ---> GIGAMONKEYS.FOO COM.INFORMATIMAGO.FOO INFORMATIMAGO.FOO
UK.CO.SMART-SOFT.FOO ---> UK.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO
Excellent point. I second that.
Also, it'd. be nice to either use the shortest nickname or to have a prefix that showed that there is "stuff" before. E.g.
COM.INFORMATIGO.FOO would be rendered as
...FOO>
Or something similar.
Cheers -- Marco Antoniotti http://bioinformatics.nyu.edu NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488 715 Broadway 10th FL fax. +1 - 212 - 998 3484 New York, NY, 10003, U.S.A.
Marco Antoniotti marcoxa@cs.nyu.edu writes:
On Aug 10, 2005, at 3:34 AM, Pascal Bourguignon wrote:
Peter Seibel writes:
FWIW, I put in that feature because I believe in using long, domain qualified package names (a la Java packages) which means that my package names are always prefaced with essentially noise. I'd much rather see:
FOO>
than:
COM.GIGAMONKEYS.FOO>
when *all* my package names start with COM.GIGAMONKEYS. But the flag is there to turn it off if you don't like (which you probably won't if you use short package names that happen to contain a dot.)
The algorithm should check for the presence of several packages with the same last part, and use more parts in these cases.
COM.GIGAMONKEYS.FOO ---> GIGAMONKEYS.FOO COM.INFORMATIMAGO.FOO INFORMATIMAGO.FOO
UK.CO.SMART-SOFT.FOO ---> UK.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO TW.CO.SMART-SOFT.FOO
Excellent point. I second that.
FWIW, I'd still like a mode where it just shows the last bit (i.e. the current behavior). To me the prompt is just a reminder what package I'm in--it doesn't need to be unambiguous. In practice I'm likely to either be in CL-USER or a package I defined. I don't really care if down in the bowels of some library there's *another* package that happens to have the same last component as mine. But obviously this is based on how I use packages and my preference for a short, clean prompt, even at the cost of some slight ambiguity. So if someone adds this feature, please allow the behavior to continue to be parameterized to support the two current modes (no contracting and contracting to last element) as well as whatever new mode you prefer.
Also, it'd. be nice to either use the shortest nickname
There is some code that tries to fall back on the shortest nickname though I'm not sure how it currently fits relative to the other contracting, mostly because I usually don't use package nicknames.
-Peter
-
Edi Weitz -
Friedrich Dominicus -
Marco Antoniotti -
Marco Baringer -
Pascal Bourguignon -
Peter Seibel