You mean you think it would work with just that line, i.e. the semantic-picolisp.el thing I created is overkill?
I suppose it would be if it wasn't for the fact that there are significant differences in syntax between elisp and picolisp. For instance, defining a function is done with de in picolisp and a class method is defined with dm.
Or did I misunderstand you?
I'm glad you found a solution. I think all you really need to do is add:
(add-hook 'picolisp-mode-hook 'semantic-default-elisp-setup)
to either your .emacs, or into semantic-el.el.
We can probably add the picolisp hook to make it a default if you find that it works well for you.
On 06/14/2011 08:11 AM, Henrik Sarvell wrote:
Thanks for the help Eric.
It's funny, just after posting to the list I tried copying
semantic-el.el to semantic-picolisp.el and changing it as required to
work for PicoLisp and that did the trick, more here:
Probably not the cleanest solution but it works.
On Tue, Jun 14, 2011 at 6:33 PM, Eric M. Ludlam <email@example.comThen I created picolisp.by <http://picolisp.by> and<mailto:firstname.lastname@example.org>> wrote:
I don't know much about picolisp, but if it is similar to Emacs
Lisp and common Lisp, then you can probably do the same thing in
semantic-el.el, and at the very end of that file, add a new hook
similar to the one that is there for common lisp.
If that works, then you are in good shape.
As for the error, I think semantic-scm may have not been updated
for the new tag formatting functions. Here is a revised version:
scheme-mode (tag &optional parent color)
"Return a prototype for the Emacs Lisp nonterminal TAG."
(let* ((tok (semantic-tag-class tag))
(args (semantic-tag-components tag))
(if (eq tok 'function)
(concat (semantic-tag-name tag) " ("
(mapconcat (lambda (a) a) args " ")
(semantic-format-tag-prototype-default tag parent color))))
I'd try just using the regular lisp parser first, which should be ok
so long as the lexical syntax is the same as Emacs Lisp.
On 06/04/2011 10:40 AM, Henrik Sarvell wrote:
I am "successfully" using CEDET with Clojure, successfully in
that if I open a Clojure file I get the function list for it in
function/method buffer so I can easily browse to any given
well as see which functions are defined.
I have no idea how this works since I can't find any Clojure
lexers/parsers in the semantic/bovine/wisent folders.
Anyway, this code browsing feature is what I'm looking for but for
PicoLisp ( http://picolisp.com ) too.
There already is a major mode for picolisp which seems to be working
fine with regards to the instructions here:
http://cedet.sourceforge.net/addlang.shtml in the sense that it
to be doing all that is required there.
simply based them on scheme.by <http://scheme.by> and
semantic-picolisp.el (attached), I<mailto:Cedetemail@example.com>
semantic-scm.el as I don't know
anything about these things.
These files generated the attached semantic-picolisp-by.el file.
Firing up emacs and editing a file will however not display any
defined functions in the method buffer.
When i run semantic-test-all-format-tag-functions I get what you see
in the attached screenshot.
I run it when I have the attached simple.l open.
Any ideas? It's a simple lisp we're talking about here so maybe
there's some shortcut that will make the function buffer work
without launching a completely new parser (thinking about why it
with clojure despite there not being any dedicated parser...)
Thanks in advance!
Simplify data backup and recovery for your virtual environment
Installation's a snap, and flexible recovery options mean your
data is safe,
secure and there when you need it. Discover what all the
Get your free trial download today.
Cedet-devel mailing list
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
Cedet-devel mailing list