Attached (this time) some more refinements for Doxygen with 'C' dealing
with [in,out] labelling of parameters.

Similar will apply to cpp.

Jon.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Author : $Author$
; Created By : Jon Green
; Created : Wed Nov 8 21:32:44 2006
; Last Modified : <070324.1608>
;
; Description : Override the C template.
; - Change the margin indent to 40 for comment align.
; - Extend Doxygen to highlight the parameter name not just the keyword.
;
; Notes : Copied and extended from hkc.emf
;
; Copyright (c) 2006 Jon Green.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; Extend the indentation to allow for margin indentation.
!if &sin "d" .fhook-c.setup
     indent .hilight.c "m" 40
!endif

; Doxygen highlighting extensions. Highlights keywords in Doxygen
!if &and &sin "h" .fhook-c.setup &band .hilight.flags 0x02
     !if &sin "l" .fhook-c.setup
         ; Create a new doxygen parameter hilighting scheme
         !if ¬ &exi .hilight.pdoxygen
             set-variable .hilight.pdoxygen &pinc .hilight.next 1
             set-variable .hilight.pdoxygencpp &pinc .hilight.next 1
         !endif
         ;
         ; Special hilighting for a 'C' parameter - branch from the doxygen
         ; space into scheme for the parameter. Note that @param is defined
         ; after the generic '@' definitions.
         ;
         ; Special for @param, @see, @retval
         hilight .hilight.cdoxygen 0x80 "[\\\\@]file"   .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]struct" .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]param"  .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]see"    .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]enum"   .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]retval" .hilight.pdoxygen
.scheme.keyword
         hilight .hilight.cdoxygen 0x80 "[\\\\@]a"      .hilight.pdoxygen
.scheme.keyword
         ; Doxygen parameter hilighting space.
         0 hilight .hilight.pdoxygen 2 50 .scheme.error
         ; Hilight the next word and finish.
         hilight .hilight.pdoxygen 0x80 "\\s+[a-zA-Z0-9.()!_\\.]+"
.hilight.cdoxygen .scheme.prepro
         ; Hilight the optional parameter definitions.
         hilight .hilight.pdoxygen 0 "\\s*\\[\\s*in\\s*\\]" .scheme.variable
         hilight .hilight.pdoxygen 0 "\\s*\\[\\s*out\\s*\\]" .scheme.variable
         hilight .hilight.pdoxygen 0 "\\s*\\[\\s*in\\s*,\\s*out\\s*\\]"
.scheme.variable
         hilight .hilight.pdoxygen 0 "\\s*\\[\\s*out\\s*,\\s*in\\s*\\]"
.scheme.variable
         ; We must return to C when we see the close of comment "*/"
         hilight .hilight.pdoxygen 0x80 "\\*/" .hilight.c .scheme.error
         ;
         ; Special hilighting for a 'C++' parameter - branch from the doxygen
         ; space into scheme for the parameter. Note that @param is defined
         ; after
         ; the generic '@' definitions.
         ;
         ; Special for @param, @see, @retval
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]a"      .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]file"   .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]struct" .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]param"  .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]see"    .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]enum"   .hilight.pdoxygencpp
.scheme.keyword
         hilight .hilight.cdoxygencpp 0x80 "[\\\\@]retval" .hilight.pdoxygencpp
.scheme.keyword
         ; Doxygen parameter hilighting space.
         0 hilight .hilight.pdoxygencpp 2 50 .scheme.error
         ; Hilight the optional parameter definitions.
         hilight .hilight.pdoxygencpp 0 "\\s*\\[\\s*in\\s*\\]" .scheme.variable
         hilight .hilight.pdoxygencpp 0 "\\s*\\[\\s*out\\s*\\]" .scheme.variable
         hilight .hilight.pdoxygencpp 0 "\\s*\\[\\s*in\\s*,\\s*out\\s*\\]"
.scheme.variable
         hilight .hilight.pdoxygencpp 0 "\\s*\\[\\s*out\\s*,\\s*in\\s*\\]"
.scheme.variable
         ; Hilight the next word and finish.
         hilight .hilight.pdoxygencpp 0x80 "\\S+[a-zA-Z0-9.()!_\\.]+"
.hilight.cdoxygencpp .scheme.prepro
         ; We must return to C when we see the close of comment "*/"
         hilight .hilight.pdoxygencpp 0x80 "$" .hilight.c .scheme.error
     !endif
     ; Pick up bogus 'C' constructs extension
     !if &sin "v" .fhook-c.setup
         ; Detect a for loop with no body - put semi-colon on next line, i.e.
         ; for (i = 1; i < 10; i++);
         ; { ... }
         hilight .hilight.c  2 "\\s\\{for[ \t]*([^()]*)[ \t]*;" .scheme.hlred
         ; Detect a bad 'if' statement that is terminated with ';' e.g.
         ; if (i < x);
         ; { ... }
         hilight .hilight.c  2 "\\s\\{if[ \t]*([^()]*)[ \t]*;"  .scheme.hlred
         ; Detect a spurious '\' at the end of the line that is
         ; not a string or #define. i.e.
         ; char *d = "This is a " \
         ;           "Duff string continuation";
         hilight .hilight.c  2 "\\\\$"                   .scheme.hlred
         ; Pick up a bad assignment in a conditional statement. e.g.
         ; if (a = SOME_CONST)
         ; while (a = SOME_CONST)
         hilight .hilight.c 2 "\\s\\{if[ \t]*([ \t]*\\w+[ \t]*=[ \t]*\\w+[ \t]*)"
.scheme.hlred
         hilight .hilight.c 2 "\\s\\{while[ \t]*([ \t]*\\w+[ \t]*=[ \t]*\\w+[
\t]*)" .scheme.hlred
     !endif
!endif

Attached some more refinements for Doxygen with 'C' dealing with
[in,out] labelling of parameters.

Similar will apply to cpp.

Jon.

Hi all,

I would like to enlarge the system wide font size for ME on Solaris.
The new 19 inch TFTs in our computer lab make the default font size (15
pt) look very tiny.
According to change-font(2) I could set thing up in my personal
.Xdefaults file, but I see no way to do that in a system wide ME global
setup file (I installed ME there) for all users. Otherwise most people
will refuse to consider ME a useful tool.

Gruß / Regards
		    Christof

--
http://badvista.fsf.org - it's time to leave!

Christof Boeckler wrote:
> Hi all,
>
> I would like to enlarge the system wide font size for ME on Solaris.
> The new 19 inch TFTs in our computer lab make the default font size (15
> pt) look very tiny.
> According to change-font(2) I could set thing up in my personal
> .Xdefaults file, but I see no way to do that in a system wide ME global
> setup file (I installed ME there) for all users. Otherwise most people
> will refuse to consider ME a useful tool.
>
> Gruß / Regards
> 		   Christof
>

Sounds like you are sysadmin on this - why not edit me.emf and add a
little start-up macro that:

a) Sets the font to new default.
b) Checks the users .Xdefaults file for a "MicroEmacs.font" entry, if it
does not exist then adds one (or creates the file if it does not exist).

I like option b) better than a) because it will not cause any re-sizze
anomalies and allows the user to change it themselves and not get your
default as part of the start-up.

Now I'm sure that writing  a macro for b) is going to be fairly easy -
but a little late for me at the moment.

i.e.
find-file ~/.Xdefaults
search-forward "^MicroEmacs.font"
if it does not exist
     end-of-buffer
     insert-string "MicroEmacs.font ..."
     save the file
endif
kill-buffer ".Xdefault"


Regards
Jon.

Jon Green wrote:
> Christof Boeckler wrote:
>> Hi all,
>>
>> I would like to enlarge the system wide font size for ME on Solaris.
>> The new 19 inch TFTs in our computer lab make the default font size (15
>> pt) look very tiny.
>> According to change-font(2) I could set thing up in my personal
>> .Xdefaults file, but I see no way to do that in a system wide ME global
>> setup file (I installed ME there) for all users. Otherwise most people
>> will refuse to consider ME a useful tool.
>>
>> Gruß / Regards
>> 		   Christof
>>
>
> Sounds like you are sysadmin on this - why not edit me.emf and add a
> little start-up macro that:
>
> a) Sets the font to new default.
> b) Checks the users .Xdefaults file for a "MicroEmacs.font" entry, if it
> does not exist then adds one (or creates the file if it does not exist).
>
> I like option b) better than a) because it will not cause any re-sizze
> anomalies and allows the user to change it themselves and not get your
> default as part of the start-up.
>
> Now I'm sure that writing  a macro for b) is going to be fairly easy -
> but a little late for me at the moment.
>
> i.e.
> find-file ~/.Xdefaults
> search-forward "^MicroEmacs.font"
> if it does not exist
>     end-of-buffer
>     insert-string "MicroEmacs.font ..."
>     save the file
> endif
> kill-buffer ".Xdefault"
>
>
> Regards
> Jon.
>

A good place to start is newuser.emf this is the start up that
configures the environment for a new user. You can probably just change
the font and force it into the session - probably easier than above.

Jon.

Hi,
while using 20060909 for 10.3 MacOS....

... accidentially managed to unbind the RETURN terminator, then had to
force-quit the shell entirely, as no amount of fiddling allowed me to
recover it.

How do I prevent that from happening in the future?

(in other words: what is the prescribed way of exiting the potentially
destructive global-unbind-key op ["esc C-k"] ?)

Also, sorry if that's an RTFM question: is there an equivalent to
ME3.9 emacs.rc file in the distribution, one executed by default upon
launch?

Thanks in advance.

Ian
this post <http://tech.groups.yahoo.com/group/jasspa/message/2247>

Ian wrote:
> Hi,
> while using 20060909 for 10.3 MacOS....
>
> ... accidentially managed to unbind the RETURN terminator, then had to
> force-quit the shell entirely, as no amount of fiddling allowed me to
> recover it.
>
> How do I prevent that from happening in the future?
>
> (in other words: what is the prescribed way of exiting the potentially
> destructive global-unbind-key op ["esc C-k"] ?)
>
> Also, sorry if that's an RTFM question: is there an equivalent to
> ME3.9 emacs.rc file in the distribution, one executed by default upon
> launch?
>
> Thanks in advance.
>
> Ian
> this post <http://tech.groups.yahoo.com/group/jasspa/message/2247>
>

Hi Ian,

I know you are transitioning across (I saw your subscribe message) - it
will take a little while to get familiar, but not long.

Hopefully you have found <user>.emf file - not sure where this lives on
a Mac, but it is in your home directory. This is equivalent to your old
ue emacs.rc (You should find it here $home/.jasspa/<user>.emf). esc-x
user-setup tells you where it is.

In the distribution macros i.e. /opt/jasspa/contrib or
/usr/share/jasspa/contrib or c:\program files\jasspa\microemacs\contrib
etc. then there is a file called "user.emf". This has lots of stuff in
it that may be useful for new users. You can copy this into your
<user>.emf in full or take bits from it and add.

Right at the bottom of this file you will see how to disable the unbind
key which is as follows:

; If you loose the C-k kill-line key then you are miss-typing and unbinding.
; Remove the global-unbind-key binding so this cannot happen.
!force global-unbind-key "esc C-k"

So add this to your <user>.emf and then restart (or do esc-x
execute-buffer to load it in).

Hope that helps.

Regards
Jon.

Below is an initial implementation of a language template for the
Groovy programming language.

cheers
-- bryan


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
;  Created By    : Bryan Schofield
;  Created       : Mon Apr 2 09:38:19 2007
;  Last Modified : <070402.0940>
;
;  Description
;   Groovy Language Template
;   http://groovy.codehaus.org
;
;  Notes
;
;  History
;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;


define-macro fhook-groovy
     set-variable $buffer-mask "luh1"
     @# buffer-init "groovy"
     buffer-init-hooks
!emacro

; buffer-init variables
set-variable .fhook-groovy.setup ® "/history/fhook/groovy" "bdfghinopx"
set-variable .fhook-groovy.setup-mask "abdefghikmnoptux"
set-variable .fhook-groovy.comment "|/*| */|*| * | * |fr|"
set-variable .fhook-groovy.comment-1 "|/**| */|*| * | * |f|"

set-variable .fhook-groovy.collapse-open  "^class"
set-variable .fhook-groovy.collapse-close "^}"
set-variable .fhook-groovy.collapse-mclose "1"
set-variable .fhook-groovy.collapse-mnext "-1"

set-variable .fhook-groovy.item-list-s1 "^[\t ]*class[\t
]+\\(\\w[1-9A-Za-z_]*\\)[\t ]*<?<?[\t ]*[A-Za-z0-9_]*"
set-variable .fhook-groovy.item-list-r1 "class \ecB\\1\ecA"
set-variable .fhook-groovy.item-list-s2 "^[\t ]*def[\t
]+\\(\\w[1-9A-Za-z_.]*\\)[\t ]*.*$"
set-variable .fhook-groovy.item-list-r2 "def \ecB\\1\ecA"

!if ¬ &exist .hilight.groovy
     set-variable .hilight.groovy  &pinc .hilight.next 1
!endif

!if &and &sin "h" .fhook-groovy.setup &band .hilight.flags 0x02
     0 hilight .hilight.groovy 0x00 $global-scheme
     ; Comments
     hilight .hilight.groovy 20 "/\\*" "*/" "" .scheme.comment
     hilight .hilight.groovy  2 "//"           .scheme.comment
     ; Comment TODO's
     hilight .hilight.groovy 20 "/\\*\\s+[Tt][Oo][Dd][Oo]" "*/" "" .scheme.error
     hilight .hilight.groovy 18 "//\\s*[tT][oO][dD][oO]"           .scheme.error

     ; Strings
     hilight .hilight.groovy  4 "\"" "\"" "\\"  .scheme.string
     hilight .hilight.groovy  4 "\'" "\'" "\\"  .scheme.string
     hilight .hilight.groovy  4 "\"\"\"" "\"\"\"" "\\"  .scheme.quote
     ; groovy string literal /.foo[0-9]\s*bar/ hiligh gets confused
with simple division.
     ;hilight .hilight.groovy  4 "/" "/" "" .scheme.quote

     ; constants: A_CONSTANT_VARAIBLE
     hilight .hilight.groovy 1    "[A-Z_]+"          .scheme.constant
     ; class names: AJavaClassName
     hilight .hilight.groovy 1    "[A-Z]+[a-z]+\\w*" .scheme.type

     ; Keywords
     hilight .hilight.groovy 0x12 "^\\s*import"       .scheme.prepro
     hilight .hilight.groovy 0x12 "^\\s*package"      .scheme.prepro
     hilight .hilight.groovy 1    "abstract"     .scheme.keyword
     hilight .hilight.groovy 1    "as"           .scheme.keyword
     hilight .hilight.groovy 1    "assert"       .scheme.keyword
     hilight .hilight.groovy 1    "boolean"      .scheme.type
     hilight .hilight.groovy 1    "break"        .scheme.operator
     hilight .hilight.groovy 1    "byte"         .scheme.type
     hilight .hilight.groovy 1    "case"         .scheme.operator
     hilight .hilight.groovy 1    "catch"        .scheme.operator
     hilight .hilight.groovy 1    "char"         .scheme.type
     hilight .hilight.groovy 1    "class"        .scheme.keyword
     hilight .hilight.groovy 1    "continue"     .scheme.operator
     hilight .hilight.groovy 1    "def"          .scheme.keyword
     hilight .hilight.groovy 1    "default"      .scheme.operator
     hilight .hilight.groovy 1    "do"           .scheme.operator
     hilight .hilight.groovy 1    "double"       .scheme.type
     hilight .hilight.groovy 1    "else"         .scheme.operator
     hilight .hilight.groovy 1    "enum"         .scheme.keyword
     hilight .hilight.groovy 1    "extends"      .scheme.keyword
     hilight .hilight.groovy 1    "false"        .scheme.constant
     hilight .hilight.groovy 1    "final"        .scheme.keyword
     hilight .hilight.groovy 1    "finally"      .scheme.operator
     hilight .hilight.groovy 1    "float"        .scheme.type
     hilight .hilight.groovy 1    "for"          .scheme.operator
     hilight .hilight.groovy 1    "if"           .scheme.operator
     hilight .hilight.groovy 1    "implements"   .scheme.keyword
     hilight .hilight.groovy 1    "import"       .scheme.keyword
     hilight .hilight.groovy 1    "in"           .scheme.operator
     hilight .hilight.groovy 1    "instanceof"   .scheme.keyword
     hilight .hilight.groovy 1    "int"          .scheme.type
     hilight .hilight.groovy 1    "interface"    .scheme.keyword
     hilight .hilight.groovy 1    "long"         .scheme.type
     hilight .hilight.groovy 1    "native"       .scheme.keyword
     hilight .hilight.groovy 1    "new"          .scheme.keyword
     hilight .hilight.groovy 1    "null"         .scheme.constant
     hilight .hilight.groovy 1    "package"      .scheme.keyword
     hilight .hilight.groovy 1    "print"        .scheme.keyword
     hilight .hilight.groovy 1    "println"      .scheme.keyword
     hilight .hilight.groovy 1    "private"      .scheme.keyword
     hilight .hilight.groovy 1    "property"     .scheme.keyword
     hilight .hilight.groovy 1    "protected"    .scheme.keyword
     hilight .hilight.groovy 1    "public"       .scheme.keyword
     hilight .hilight.groovy 1    "return"       .scheme.operator
     hilight .hilight.groovy 1    "short"        .scheme.type
     hilight .hilight.groovy 1    "static"       .scheme.keyword
     hilight .hilight.groovy 1    "strictfp"     .scheme.keyword
     hilight .hilight.groovy 1    "super"        .scheme.keyword
     hilight .hilight.groovy 1    "switch"       .scheme.operator
     hilight .hilight.groovy 1    "synchronized" .scheme.keyword
     hilight .hilight.groovy 1    "this"         .scheme.keyword
     hilight .hilight.groovy 1    "throw"        .scheme.operator
     hilight .hilight.groovy 1    "throws"       .scheme.keyword
     hilight .hilight.groovy 1    "transient"    .scheme.keyword
     hilight .hilight.groovy 1    "true"         .scheme.constant
     hilight .hilight.groovy 1    "try"          .scheme.operator
     hilight .hilight.groovy 1    "void"         .scheme.keyword
     hilight .hilight.groovy 1    "volatile"     .scheme.keyword
     hilight .hilight.groovy 1    "while"        .scheme.operator

     hilight .hilight.groovy 1    "; *$"       .scheme.error

!endif

!if &sin "d" .fhook-groovy.setup
     !if ¬ &exi .indent.groovy-comm
         set-variable .indent.groovy-comm &pinc .hilight.next 1
         set-variable .indent.groovyT &pinc .hilight.next 1
     !endif


     0 indent .indent.groovy-comm 1 20
     0 indent .indent.groovyT 1 500
     0 indent .hilight.groovy 2 20 .indent.groovyT

     ; switch to comment indentation mode
     indent .indent.groovyT t "/\\*"   .indent.groovy-comm
     indent .hilight.groovy  x "/\\*" 1 .indent.groovy-comm
     indent .indent.groovy-comm x "\\*/" -1 0
     indent .indent.groovyT t "\\*/" 0
     indent .hilight.groovy o "\\*/" -1


     ; strings
     indent .hilight.groovy e "\"" "\"" "\\"
     indent .hilight.groovy e "\'" "\'" "\\"
     ; standard braces
     indent .hilight.groovy n "{"  t
     indent .hilight.groovy o "}" -t
     indent .hilight.groovy n "(" 3/2t
     indent .hilight.groovy o ")" -3/2t

!endif

buffer-init-fhook "groovy"

Is there any short cut to insert the current buffer's file name in to
a shell command, using shell-command, pipe-shell-command, or
ipipe-shell-command? Something like vi's %?

for example,

    someScript -opt %f

There seems to be ("system") variables of

$buffer-fname

	 and

$file-names

which may be what you're looking for... see

"M-x list-variables" and/or "M-x command-apropos"

	 $buffer

Ian
this post <http://tech.groups.yahoo.com/group/jasspa/message/2251>

On 4/2/07, Bryan Schofield <schofield.bryan@...> wrote:
> Is there any short cut to insert the current buffer's file name in to
> a shell command, using shell-command, pipe-shell-command, or
> ipipe-shell-command? Something like vi's %?
>
> for example,
>
>    someScript -opt %f

I don't think there's a shortcut.

I think you're meant to construct the command string yourself.
As Ian just pointed out, list-variables shows various variables that
hold various forms of the filename.

If you want not to have to worry about the filename, maybe try
pipe-shell-command (and supply your own result buffer name to catch the
results).

-Th


Bryan Schofield wrote:
> Is there any short cut to insert the current buffer's file name in to
> a shell command, using shell-command, pipe-shell-command, or
> ipipe-shell-command? Something like vi's %?
>
> for example,
>
>    someScript -opt %f
>

---

From: jasspa@yahoogroups.com [mailto:jasspa@yahoogroups.com] On Behalf Of Thomas Hundt
Sent: Tuesday, April 03, 2007 1:35 AM
To: jasspa@yahoogroups.com
Subject: Re: [jasspa] shell commands

I don't think there's a shortcut.

I think you're meant to construct the command string yourself.
As Ian just pointed out, list-variables shows various variables that
hold various forms of the filename.

If you want not to have to worry about the filename, maybe try
pipe-shell-command (and supply your own result buffer name to catch the
results).

-Th

Bryan Schofield wrote:
> Is there any short cut to insert the current buffer's file name in to
> a shell command, using shell-command, pipe-shell-command, or
> ipipe-shell-command? Something like vi's %?
>
> for example,
>
> someScript -opt %f
>

The Notes help (help-command notes) indicates "Rename Note" is bound
to "n", but it is really bound to "e", "Forward Note" is bound to "n".

Hi all,
I don't use often the file-browser but, under linux (32 and 64 bit),
me crash when I select symbolic link. Some of you have the same
problem?

Ciao.

Vincenzo

ZarathustraXYZ wrote:
> Hi all,
> I don't use often the file-browser but, under linux (32 and 64 bit),
> me crash when I select symbolic link. Some of you have the same
> problem?
>
> Ciao.
>
> Vincenzo
>
>

Is there a circular symbolic link in the directory?

No.
glibc say: *** glibc detected *** double free or corruption (!prev):
0x00000000006f4920 ***
Aborted


--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> ZarathustraXYZ wrote:
> > Hi all,
> > I don't use often the file-browser but, under linux (32 and 64
bit),
> > me crash when I select symbolic link. Some of you have the same
> > problem?
> >
> > Ciao.
> >
> > Vincenzo
> >
> >
>
> Is there a circular symbolic link in the directory?
>

FYI It's working for me (SuSE 32-bit) and it's been very stable over the
past few years.  What versions are you using?

One thing I'd ask is, when you hit F10 to bring up the file browser,
does it recognize the symbolic links?  (It should display for example
"HackSym/ -> Hack" for a link created using 'ln -s Hack HackSym'.)

How far does it get when it crashes?  When you click on (or hit Return
on) one of these entries, it says at the bottom, "[Evaluating <item>]".
   It also changes the directory tree display on the left to show the
directories in the selected dir.  And it changes the pane on the right
to show the directories and files.

-Th


ZarathustraXYZ wrote, On 5/28/2007 3:51 AM:
> No.
> glibc say: *** glibc detected *** double free or corruption (!prev):
> 0x00000000006f4920 ***
> Aborted
>
>
> --- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>> ZarathustraXYZ wrote:
>>> Hi all,
>>> I don't use often the file-browser but, under linux (32 and 64
> bit),
>>> me crash when I select symbolic link. Some of you have the same
>>> problem?
>>>
>>> Ciao.
>>>
>>> Vincenzo
>>>
>>>
>> Is there a circular symbolic link in the directory?
>>
>
--
Thomas Hundt <tom@...> +1-415-867-6698

Thomas Hundt wrote:
> FYI It's working for me (SuSE 32-bit) and it's been very stable over the
> past few years.  What versions are you using?
>
> One thing I'd ask is, when you hit F10 to bring up the file browser,
> does it recognize the symbolic links?  (It should display for example
> "HackSym/ -> Hack" for a link created using 'ln -s Hack HackSym'.)
>
> How far does it get when it crashes?  When you click on (or hit Return
> on) one of these entries, it says at the bottom, "[Evaluating <item>]".
>   It also changes the directory tree display on the left to show the
> directories in the selected dir.  And it changes the pane on the right
> to show the directories and files.
>
> -Th
>

Good point, I wonder if there is an incompatibility with the linked
glibc.so? Maybe need to build from source to correct the problem. The
current version is distributed with Gentoo and there do not seem to be
any problems with Linux.

Strongly suggest a source re-build and see how it goes on your system.

I was going to try building this on CentOs 5.0 to see what happens -
will do this later in the week.

Jon.

Hi,
file-browser recognize the symbolic links. On amd64 when I click (on
when I hit Return) crash without display nothing at the bottom (on
fedora 6 and  centos 4.5 on amd64), maybe it's to fast I guess. On
ScientificLinux 4.5 (32 bit) it say at the
bottom "[Evaluating ... " .
I have rebuilded Me from source (my gcc is gcc version 4.1.1
20070105 (Red Hat 4.1.1-51) and glibc is  glibc-2.5-10.fc6.x86_64)
but this is the result :-( :

*** glibc detected *** ./me: double free or corruption (!prev):
0x00000000006d1700 ***
======= Backtrace: =========
/lib64/libc.so.6[0x396086ea30]
/lib64/libc.so.6(cfree+0x8c)[0x396087214c]
./me[0x40baac]
./me[0x40c6ef]
./me[0x40cb03]
./me[0x41a91d]
./me[0x41b791]
./me[0x41bd4b]
./me[0x41a8b6]
./me[0x41b791]
./me[0x41bd4b]
./me[0x41a8b6]
./me[0x41b791]
./me[0x41cb0c]
./me[0x41a91d]
./me[0x41b791]
./me[0x41bd4b]
./me[0x41a8b6]
./me[0x43a8f4]
./me[0x43ae41]
./me[0x43aee0]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x396081da44]
./me[0x403a09]
======= Memory map: ========
00400000-00487000 r-xp 00000000 08:04
328162                            
/home/enzo/Programmi/microemacs/me060909/src/me
00686000-0068f000 rw-p 00086000 08:04
328162                            
/home/enzo/Programmi/microemacs/me060909/src/me
0068f000-00738000 rw-p 0068f000 00:00 0
[heap]
3688000000-3688104000 r-xp 00000000 08:03
3106358                        /usr/lib64/libX11.so.6.2.0
3688104000-3688304000 ---p 00104000 08:03
3106358                        /usr/lib64/libX11.so.6.2.0
3688304000-368830b000 rw-p 00104000 08:03
3106358                        /usr/lib64/libX11.so.6.2.0
3688800000-3688809000 r-xp 00000000 08:03
3127047                        /usr/lib64/libXrender.so.1.3.0
3688809000-3688a08000 ---p 00009000 08:03
3127047                        /usr/lib64/libXrender.so.1.3.0
3688a08000-3688a09000 rw-p 00008000 08:03
3127047                        /usr/lib64/libXrender.so.1.3.0
3689000000-368900a000 r-xp 00000000 08:03
3127050                        /usr/lib64/libXcursor.so.1.0.2
368900a000-3689209000 ---p 0000a000 08:03
3127050                        /usr/lib64/libXcursor.so.1.0.2
3689209000-368920a000 rw-p 00009000 08:03
3127050                        /usr/lib64/libXcursor.so.1.0.2
3689400000-3689410000 r-xp 00000000 08:03
3114633                        /usr/lib64/libXpm.so.4.11.0
3689410000-3689610000 ---p 00010000 08:03
3114633                        /usr/lib64/libXpm.so.4.11.0
3689610000-3689611000 rw-p 00010000 08:03
3114633                        /usr/lib64/libXpm.so.4.11.0
3689800000-3689805000 r-xp 00000000 08:03
3127049                        /usr/lib64/libXfixes.so.3.1.0
3689805000-3689a04000 ---p 00005000 08:03
3127049                        /usr/lib64/libXfixes.so.3.1.0
3689a04000-3689a05000 rw-p 00004000 08:03
3127049                        /usr/lib64/libXfixes.so.3.1.0
3960400000-396041a000 r-xp 00000000 08:03
1109786                        /lib64/ld-2.5.so
3960619000-396061a000 r--p 00019000 08:03
1109786                        /lib64/ld-2.5.so
396061a000-396061b000 rw-p 0001a000 08:03
1109786                        /lib64/ld-2.5.so
3960800000-3960944000 r-xp 00000000 08:03
1109788                        /lib64/libc-2.5.so
3960944000-3960b44000 ---p 00144000 08:03
1109788                        /lib64/libc-2.5.so
3960b44000-3960b48000 r--p 00144000 08:03
1109788                        /lib64/libc-2.5.so
3960b48000-3960b49000 rw-p 00148000 08:03
1109788                        /lib64/libc-2.5.so
3960b49000-3960b4e000 rw-p 3960b49000 00:00 0
3961000000-3961003000 r-xp 00000000 08:03
1109804                        /lib64/libdl-2.5.so
3961003000-3961202000 ---p 00003000 08:03
1109804                        /lib64/libdl-2.5.so
3961202000-3961203000 r--p 00002000 08:03
1109804                        /lib64/libdl-2.5.so
3961203000-3961204000 rw-p 00003000 08:03
1109804                        /lib64/libdl-2.5.so
3961c00000-3961c0d000 r-xp 00000000 08:03
1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
3961c0d000-3961e0c000 ---p 0000d000 08:03
1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
3961e0c000-3961e0d000 rw-p 0000c000 08:03
1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
3962400000-3962402000 r-xp 00000000 08:03
3125619                        /usr/lib64/libXau.so.6.0.0
3962402000-3962601000 ---p 00002000 08:03
3125619                        /usr/lib64/libXau.so.6.0.0
3962601000-3962602Aborted

Ciao.

Vincenzo



--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> Thomas Hundt wrote:
> > FYI It's working for me (SuSE 32-bit) and it's been very stable
over the
> > past few years.  What versions are you using?
> >
> > One thing I'd ask is, when you hit F10 to bring up the file
browser,
> > does it recognize the symbolic links?  (It should display for
example
> > "HackSym/ -> Hack" for a link created using 'ln -s Hack
HackSym'.)
> >
> > How far does it get when it crashes?  When you click on (or hit
Return
> > on) one of these entries, it says at the bottom, "[Evaluating
<item>]".
> >   It also changes the directory tree display on the left to show
the
> > directories in the selected dir.  And it changes the pane on the
right
> > to show the directories and files.
> >
> > -Th
> >
>
> Good point, I wonder if there is an incompatibility with the
linked
> glibc.so? Maybe need to build from source to correct the problem.
The
> current version is distributed with Gentoo and there do not seem
to be
> any problems with Linux.
>
> Strongly suggest a source re-build and see how it goes on your
system.
>
> I was going to try building this on CentOs 5.0 to see what
happens -
> will do this later in the week.
>
> Jon.
>

Ok, I have found where is the problem.
I didn't realize it before but the link that crash Me
is "strange" :-),  this is the output of ls -l:

lrwxrwxrwx  1 enzo   enzo         11 27 mag 00:35 webservice ->
WebService//
drwxrwxr-x 24 enzo   enzo       2000 12 mag 23:27 WebService/

Due to a typing error i have made this link.
I can use this link with all other application but not with Me.

Ciao.

Vincenzo




--- In jasspa@yahoogroups.com, "ZarathustraXYZ" <zarathustraxyz@...>
wrote:
>
> Hi,
> file-browser recognize the symbolic links. On amd64 when I click
(on
> when I hit Return) crash without display nothing at the bottom (on
> fedora 6 and  centos 4.5 on amd64), maybe it's to fast I guess. On
> ScientificLinux 4.5 (32 bit) it say at the
> bottom "[Evaluating ... " .
> I have rebuilded Me from source (my gcc is gcc version 4.1.1
> 20070105 (Red Hat 4.1.1-51) and glibc is  glibc-2.5-10.fc6.x86_64)
> but this is the result :-( :
>
> *** glibc detected *** ./me: double free or corruption (!prev):
> 0x00000000006d1700 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x396086ea30]
> /lib64/libc.so.6(cfree+0x8c)[0x396087214c]
> ./me[0x40baac]
> ./me[0x40c6ef]
> ./me[0x40cb03]
> ./me[0x41a91d]
> ./me[0x41b791]
> ./me[0x41bd4b]
> ./me[0x41a8b6]
> ./me[0x41b791]
> ./me[0x41bd4b]
> ./me[0x41a8b6]
> ./me[0x41b791]
> ./me[0x41cb0c]
> ./me[0x41a91d]
> ./me[0x41b791]
> ./me[0x41bd4b]
> ./me[0x41a8b6]
> ./me[0x43a8f4]
> ./me[0x43ae41]
> ./me[0x43aee0]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x396081da44]
> ./me[0x403a09]
> ======= Memory map: ========
> 00400000-00487000 r-xp 00000000 08:04
>
328162                            
/home/enzo/Programmi/microemacs/me060909/src/me
> 00686000-0068f000 rw-p 00086000 08:04
>
328162                            
/home/enzo/Programmi/microemacs/me060909/src/me
> 0068f000-00738000 rw-p 0068f000 00:00 0
> [heap]
> 3688000000-3688104000 r-xp 00000000 08:03
> 3106358                        /usr/lib64/libX11.so.6.2.0
> 3688104000-3688304000 ---p 00104000 08:03
> 3106358                        /usr/lib64/libX11.so.6.2.0
> 3688304000-368830b000 rw-p 00104000 08:03
> 3106358                        /usr/lib64/libX11.so.6.2.0
> 3688800000-3688809000 r-xp 00000000 08:03
> 3127047                        /usr/lib64/libXrender.so.1.3.0
> 3688809000-3688a08000 ---p 00009000 08:03
> 3127047                        /usr/lib64/libXrender.so.1.3.0
> 3688a08000-3688a09000 rw-p 00008000 08:03
> 3127047                        /usr/lib64/libXrender.so.1.3.0
> 3689000000-368900a000 r-xp 00000000 08:03
> 3127050                        /usr/lib64/libXcursor.so.1.0.2
> 368900a000-3689209000 ---p 0000a000 08:03
> 3127050                        /usr/lib64/libXcursor.so.1.0.2
> 3689209000-368920a000 rw-p 00009000 08:03
> 3127050                        /usr/lib64/libXcursor.so.1.0.2
> 3689400000-3689410000 r-xp 00000000 08:03
> 3114633                        /usr/lib64/libXpm.so.4.11.0
> 3689410000-3689610000 ---p 00010000 08:03
> 3114633                        /usr/lib64/libXpm.so.4.11.0
> 3689610000-3689611000 rw-p 00010000 08:03
> 3114633                        /usr/lib64/libXpm.so.4.11.0
> 3689800000-3689805000 r-xp 00000000 08:03
> 3127049                        /usr/lib64/libXfixes.so.3.1.0
> 3689805000-3689a04000 ---p 00005000 08:03
> 3127049                        /usr/lib64/libXfixes.so.3.1.0
> 3689a04000-3689a05000 rw-p 00004000 08:03
> 3127049                        /usr/lib64/libXfixes.so.3.1.0
> 3960400000-396041a000 r-xp 00000000 08:03
> 1109786                        /lib64/ld-2.5.so
> 3960619000-396061a000 r--p 00019000 08:03
> 1109786                        /lib64/ld-2.5.so
> 396061a000-396061b000 rw-p 0001a000 08:03
> 1109786                        /lib64/ld-2.5.so
> 3960800000-3960944000 r-xp 00000000 08:03
> 1109788                        /lib64/libc-2.5.so
> 3960944000-3960b44000 ---p 00144000 08:03
> 1109788                        /lib64/libc-2.5.so
> 3960b44000-3960b48000 r--p 00144000 08:03
> 1109788                        /lib64/libc-2.5.so
> 3960b48000-3960b49000 rw-p 00148000 08:03
> 1109788                        /lib64/libc-2.5.so
> 3960b49000-3960b4e000 rw-p 3960b49000 00:00 0
> 3961000000-3961003000 r-xp 00000000 08:03
> 1109804                        /lib64/libdl-2.5.so
> 3961003000-3961202000 ---p 00003000 08:03
> 1109804                        /lib64/libdl-2.5.so
> 3961202000-3961203000 r--p 00002000 08:03
> 1109804                        /lib64/libdl-2.5.so
> 3961203000-3961204000 rw-p 00003000 08:03
> 1109804                        /lib64/libdl-2.5.so
> 3961c00000-3961c0d000 r-xp 00000000 08:03
> 1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
> 3961c0d000-3961e0c000 ---p 0000d000 08:03
> 1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
> 3961e0c000-3961e0d000 rw-p 0000c000 08:03
> 1110040                        /lib64/libgcc_s-4.1.1-20070105.so.1
> 3962400000-3962402000 r-xp 00000000 08:03
> 3125619                        /usr/lib64/libXau.so.6.0.0
> 3962402000-3962601000 ---p 00002000 08:03
> 3125619                        /usr/lib64/libXau.so.6.0.0
> 3962601000-3962602Aborted
>
> Ciao.
>
> Vincenzo
>
>
>
> --- In jasspa@yahoogroups.com, Jon Green <jon@> wrote:
> >
> > Thomas Hundt wrote:
> > > FYI It's working for me (SuSE 32-bit) and it's been very
stable
> over the
> > > past few years.  What versions are you using?
> > >
> > > One thing I'd ask is, when you hit F10 to bring up the file
> browser,
> > > does it recognize the symbolic links?  (It should display for
> example
> > > "HackSym/ -> Hack" for a link created using 'ln -s Hack
> HackSym'.)
> > >
> > > How far does it get when it crashes?  When you click on (or
hit
> Return
> > > on) one of these entries, it says at the bottom, "[Evaluating
> <item>]".
> > >   It also changes the directory tree display on the left to
show
> the
> > > directories in the selected dir.  And it changes the pane on
the
> right
> > > to show the directories and files.
> > >
> > > -Th
> > >
> >
> > Good point, I wonder if there is an incompatibility with the
> linked
> > glibc.so? Maybe need to build from source to correct the
problem.
> The
> > current version is distributed with Gentoo and there do not seem
> to be
> > any problems with Linux.
> >
> > Strongly suggest a source re-build and see how it goes on your
> system.
> >
> > I was going to try building this on CentOs 5.0 to see what
> happens -
> > will do this later in the week.
> >
> > Jon.
> >
>

ZarathustraXYZ wrote:
> Ok, I have found where is the problem.
> I didn't realize it before but the link that crash Me
> is "strange" :-),  this is the output of ls -l:
>
> lrwxrwxrwx  1 enzo   enzo         11 27 mag 00:35 webservice ->
> WebService//
> drwxrwxr-x 24 enzo   enzo       2000 12 mag 23:27 WebService/
>
> Due to a typing error i have made this link.
> I can use this link with all other application but not with Me.
>

So if you fix the link does this fix the problem? (not that this is an
excuse).

> Ciao.
>
> Vincenzo
>

Cool link.

Does not crash on Solaris with this type of link.
I will have to build on Linux and debug it.

What you should of got is this:

Directory listing of: /home/jon/crash/
      10240  used in 0 files and 4 dirs (Not-Filtered)

   Attr    Size             Modified Name  <Order by Extension>
   drwx    8704  2007/05/28 22:20:13 ../
   drwx     512  2007/05/28 22:20:29 WebService/
   drwx     512  2007/05/28 22:20:29 webservice/ -> WebService//

Following the link in the browser descends to the next directory. I
think I have reproduced it correctly as you stated above:

cd /home/jon/crash/
ls -la

total 24
drwxr-xr-x   3 jon      users        512 May 28 22:20 .
drwxr-x--- 108 jon      users       8704 May 28 22:20 ..
lrwxrwxrwx   1 jon      users         12 May 28 22:20 webservice ->
WebService//
drwxr-xr-x   2 jon      users        512 May 28 22:20 WebService
[EXIT 0]

Thanks for the info.
Regards
Jon.

I think I found and fixed this issue. Now that you have built ME
yourself, could you please try the following fix and let me know if it
solves the problem. Note the line numbers may not be exactly right as I
had make other commits before this one. Thanks,

Steve

Index: dirlist.c
===================================================================
RCS file: /usr/cvs/repme/me/src/dirlist.c,v
retrieving revision 2.12
retrieving revision 2.13
diff -c -w -r2.12 -r2.13
*** dirlist.c    22 Oct 2006 16:43:14 -0000    2.12
--- dirlist.c    26 Oct 2006 20:01:23 -0000    2.13
***************
*** 166,172 ****
       /* Recursively iterate over the children and delete */
       for (dnode = root->child; dnode != NULL; /* NULL */)
       {
!         if(dnode->child != NULL)
               dirDeleteTree (dnode);
           dt = dnode;                     /* Remember node to delete */
           dnode = dnode->next ;           /* Point to next node */
--- 166,172 ----
       /* Recursively iterate over the children and delete */
       for (dnode = root->child; dnode != NULL; /* NULL */)
       {
!         if((dnode->child != NULL) && (dnode->lname == NULL))
               dirDeleteTree (dnode);
           dt = dnode;                     /* Remember node to delete */
           dnode = dnode->next ;           /* Point to next node */
***************

ZarathustraXYZ wrote:
>
> Ok, I have found where is the problem.
> I didn't realize it before but the link that crash Me
> is "strange" :-), this is the output of ls -l:
>
> lrwxrwxrwx 1 enzo enzo 11 27 mag 00:35 webservice ->
> WebService//
> drwxrwxr-x 24 enzo enzo 2000 12 mag 23:27 WebService/
>
> Due to a typing error i have made this link.
> I can use this link with all other application but not with Me.
>
> Ciao.
>
> Vincenzo
>
> --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>,
> "ZarathustraXYZ" <zarathustraxyz@...>
> wrote:
> >
> > Hi,
> > file-browser recognize the symbolic links. On amd64 when I click
> (on
> > when I hit Return) crash without display nothing at the bottom (on
> > fedora 6 and centos 4.5 on amd64), maybe it's to fast I guess. On
> > ScientificLinux 4.5 (32 bit) it say at the
> > bottom "[Evaluating ... " .
> > I have rebuilded Me from source (my gcc is gcc version 4.1.1
> > 20070105 (Red Hat 4.1.1-51) and glibc is glibc-2.5-10.fc6.x86_64)
> > but this is the result :-( :
> >
> > *** glibc detected *** ./me: double free or corruption (!prev):
> > 0x00000000006d1700 ***
> > ======= Backtrace: =========
> > /lib64/libc.so.6[0x396086ea30]
> > /lib64/libc.so.6(cfree+0x8c)[0x396087214c]
> > ./me[0x40baac]
> > ./me[0x40c6ef]
> > ./me[0x40cb03]
> > ./me[0x41a91d]
> > ./me[0x41b791]
> > ./me[0x41bd4b]
> > ./me[0x41a8b6]
> > ./me[0x41b791]
> > ./me[0x41bd4b]
> > ./me[0x41a8b6]
> > ./me[0x41b791]
> > ./me[0x41cb0c]
> > ./me[0x41a91d]
> > ./me[0x41b791]
> > ./me[0x41bd4b]
> > ./me[0x41a8b6]
> > ./me[0x43a8f4]
> > ./me[0x43ae41]
> > ./me[0x43aee0]
> > /lib64/libc.so.6(__libc_start_main+0xf4)[0x396081da44]
> > ./me[0x403a09]
> > ======= Memory map: ========
> > 00400000-00487000 r-xp 00000000 08:04
> >
> 328162 /home/enzo/Programmi/microemacs/me060909/src/me
> > 00686000-0068f000 rw-p 00086000 08:04
> >
> 328162 /home/enzo/Programmi/microemacs/me060909/src/me
> > 0068f000-00738000 rw-p 0068f000 00:00 0
> > [heap]
> > 3688000000-3688104000 r-xp 00000000 08:03
> > 3106358 /usr/lib64/libX11.so.6.2.0
> > 3688104000-3688304000 ---p 00104000 08:03
> > 3106358 /usr/lib64/libX11.so.6.2.0
> > 3688304000-368830b000 rw-p 00104000 08:03
> > 3106358 /usr/lib64/libX11.so.6.2.0
> > 3688800000-3688809000 r-xp 00000000 08:03
> > 3127047 /usr/lib64/libXrender.so.1.3.0
> > 3688809000-3688a08000 ---p 00009000 08:03
> > 3127047 /usr/lib64/libXrender.so.1.3.0
> > 3688a08000-3688a09000 rw-p 00008000 08:03
> > 3127047 /usr/lib64/libXrender.so.1.3.0
> > 3689000000-368900a000 r-xp 00000000 08:03
> > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > 368900a000-3689209000 ---p 0000a000 08:03
> > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > 3689209000-368920a000 rw-p 00009000 08:03
> > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > 3689400000-3689410000 r-xp 00000000 08:03
> > 3114633 /usr/lib64/libXpm.so.4.11.0
> > 3689410000-3689610000 ---p 00010000 08:03
> > 3114633 /usr/lib64/libXpm.so.4.11.0
> > 3689610000-3689611000 rw-p 00010000 08:03
> > 3114633 /usr/lib64/libXpm.so.4.11.0
> > 3689800000-3689805000 r-xp 00000000 08:03
> > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > 3689805000-3689a04000 ---p 00005000 08:03
> > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > 3689a04000-3689a05000 rw-p 00004000 08:03
> > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > 3960400000-396041a000 r-xp 00000000 08:03
> > 1109786 /lib64/ld-2.5.so
> > 3960619000-396061a000 r--p 00019000 08:03
> > 1109786 /lib64/ld-2.5.so
> > 396061a000-396061b000 rw-p 0001a000 08:03
> > 1109786 /lib64/ld-2.5.so
> > 3960800000-3960944000 r-xp 00000000 08:03
> > 1109788 /lib64/libc-2.5.so
> > 3960944000-3960b44000 ---p 00144000 08:03
> > 1109788 /lib64/libc-2.5.so
> > 3960b44000-3960b48000 r--p 00144000 08:03
> > 1109788 /lib64/libc-2.5.so
> > 3960b48000-3960b49000 rw-p 00148000 08:03
> > 1109788 /lib64/libc-2.5.so
> > 3960b49000-3960b4e000 rw-p 3960b49000 00:00 0
> > 3961000000-3961003000 r-xp 00000000 08:03
> > 1109804 /lib64/libdl-2.5.so
> > 3961003000-3961202000 ---p 00003000 08:03
> > 1109804 /lib64/libdl-2.5.so
> > 3961202000-3961203000 r--p 00002000 08:03
> > 1109804 /lib64/libdl-2.5.so
> > 3961203000-3961204000 rw-p 00003000 08:03
> > 1109804 /lib64/libdl-2.5.so
> > 3961c00000-3961c0d000 r-xp 00000000 08:03
> > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > 3961c0d000-3961e0c000 ---p 0000d000 08:03
> > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > 3961e0c000-3961e0d000 rw-p 0000c000 08:03
> > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > 3962400000-3962402000 r-xp 00000000 08:03
> > 3125619 /usr/lib64/libXau.so.6.0.0
> > 3962402000-3962601000 ---p 00002000 08:03
> > 3125619 /usr/lib64/libXau.so.6.0.0
> > 3962601000-3962602Aborted
> >
> > Ciao.
> >
> > Vincenzo
> >
> >
> >
> > --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>, Jon
> Green <jon@> wrote:
> > >
> > > Thomas Hundt wrote:
> > > > FYI It's working for me (SuSE 32-bit) and it's been very
> stable
> > over the
> > > > past few years. What versions are you using?
> > > >
> > > > One thing I'd ask is, when you hit F10 to bring up the file
> > browser,
> > > > does it recognize the symbolic links? (It should display for
> > example
> > > > "HackSym/ -> Hack" for a link created using 'ln -s Hack
> > HackSym'.)
> > > >
> > > > How far does it get when it crashes? When you click on (or
> hit
> > Return
> > > > on) one of these entries, it says at the bottom, "[Evaluating
> > <item>]".
> > > > It also changes the directory tree display on the left to
> show
> > the
> > > > directories in the selected dir. And it changes the pane on
> the
> > right
> > > > to show the directories and files.
> > > >
> > > > -Th
> > > >
> > >
> > > Good point, I wonder if there is an incompatibility with the
> > linked
> > > glibc.so? Maybe need to build from source to correct the
> problem.
> > The
> > > current version is distributed with Gentoo and there do not seem
> > to be
> > > any problems with Linux.
> > >
> > > Strongly suggest a source re-build and see how it goes on your
> > system.
> > >
> > > I was going to try building this on CentOs 5.0 to see what
> > happens -
> > > will do this later in the week.
> > >
> > > Jon.
> > >
> >
>
>

Yes, if I fix the link Me work fine.

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> ZarathustraXYZ wrote:
> > Ok, I have found where is the problem.
> > I didn't realize it before but the link that crash Me
> > is "strange" :-),  this is the output of ls -l:
> >
> > lrwxrwxrwx  1 enzo   enzo         11 27 mag 00:35 webservice ->
> > WebService//
> > drwxrwxr-x 24 enzo   enzo       2000 12 mag 23:27 WebService/
> >
> > Due to a typing error i have made this link.
> > I can use this link with all other application but not with Me.
> >
>
> So if you fix the link does this fix the problem? (not that this
is an
> excuse).
>
> > Ciao.
> >
> > Vincenzo
> >
>
> Cool link.
>
> Does not crash on Solaris with this type of link.
> I will have to build on Linux and debug it.
>
> What you should of got is this:
>
> Directory listing of: /home/jon/crash/
>      10240  used in 0 files and 4 dirs (Not-Filtered)
>
>   Attr    Size             Modified Name  <Order by Extension>
>   drwx    8704  2007/05/28 22:20:13 ../
>   drwx     512  2007/05/28 22:20:29 WebService/
>   drwx     512  2007/05/28 22:20:29 webservice/ -> WebService//
>
> Following the link in the browser descends to the next directory.
I
> think I have reproduced it correctly as you stated above:
>
> cd /home/jon/crash/
> ls -la
>
> total 24
> drwxr-xr-x   3 jon      users        512 May 28 22:20 .
> drwxr-x--- 108 jon      users       8704 May 28 22:20 ..
> lrwxrwxrwx   1 jon      users         12 May 28 22:20
webservice ->
> WebService//
> drwxr-xr-x   2 jon      users        512 May 28 22:20 WebService
> [EXIT 0]
>
> Thanks for the info.
> Regards
> Jon.
>

Your patch partially fix. Now Me don't crash but in the dir tree
show the root-dir folded.

Ciao.

Vincenzo

--- In jasspa@yahoogroups.com, Steven Phillips <bill@...> wrote:
>
> I think I found and fixed this issue. Now that you have built ME
> yourself, could you please try the following fix and let me know
if it
> solves the problem. Note the line numbers may not be exactly right
as I
> had make other commits before this one. Thanks,
>
> Steve
>
> Index: dirlist.c
>
===================================================================
> RCS file: /usr/cvs/repme/me/src/dirlist.c,v
> retrieving revision 2.12
> retrieving revision 2.13
> diff -c -w -r2.12 -r2.13
> *** dirlist.c    22 Oct 2006 16:43:14 -0000    2.12
> --- dirlist.c    26 Oct 2006 20:01:23 -0000    2.13
> ***************
> *** 166,172 ****
>       /* Recursively iterate over the children and delete */
>       for (dnode = root->child; dnode != NULL; /* NULL */)
>       {
> !         if(dnode->child != NULL)
>               dirDeleteTree (dnode);
>           dt = dnode;                     /* Remember node to
delete */
>           dnode = dnode->next ;           /* Point to next node */
> --- 166,172 ----
>       /* Recursively iterate over the children and delete */
>       for (dnode = root->child; dnode != NULL; /* NULL */)
>       {
> !         if((dnode->child != NULL) && (dnode->lname == NULL))
>               dirDeleteTree (dnode);
>           dt = dnode;                     /* Remember node to
delete */
>           dnode = dnode->next ;           /* Point to next node */
> ***************
>
> ZarathustraXYZ wrote:
> >
> > Ok, I have found where is the problem.
> > I didn't realize it before but the link that crash Me
> > is "strange" :-), this is the output of ls -l:
> >
> > lrwxrwxrwx 1 enzo enzo 11 27 mag 00:35 webservice ->
> > WebService//
> > drwxrwxr-x 24 enzo enzo 2000 12 mag 23:27 WebService/
> >
> > Due to a typing error i have made this link.
> > I can use this link with all other application but not with Me.
> >
> > Ciao.
> >
> > Vincenzo
> >
> > --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>,
> > "ZarathustraXYZ" <zarathustraxyz@>
> > wrote:
> > >
> > > Hi,
> > > file-browser recognize the symbolic links. On amd64 when I
click
> > (on
> > > when I hit Return) crash without display nothing at the bottom
(on
> > > fedora 6 and centos 4.5 on amd64), maybe it's to fast I guess.
On
> > > ScientificLinux 4.5 (32 bit) it say at the
> > > bottom "[Evaluating ... " .
> > > I have rebuilded Me from source (my gcc is gcc version 4.1.1
> > > 20070105 (Red Hat 4.1.1-51) and glibc is
glibc-2.5-10.fc6.x86_64)
> > > but this is the result :-( :
> > >
> > > *** glibc detected *** ./me: double free or corruption
(!prev):
> > > 0x00000000006d1700 ***
> > > ======= Backtrace: =========
> > > /lib64/libc.so.6[0x396086ea30]
> > > /lib64/libc.so.6(cfree+0x8c)[0x396087214c]
> > > ./me[0x40baac]
> > > ./me[0x40c6ef]
> > > ./me[0x40cb03]
> > > ./me[0x41a91d]
> > > ./me[0x41b791]
> > > ./me[0x41bd4b]
> > > ./me[0x41a8b6]
> > > ./me[0x41b791]
> > > ./me[0x41bd4b]
> > > ./me[0x41a8b6]
> > > ./me[0x41b791]
> > > ./me[0x41cb0c]
> > > ./me[0x41a91d]
> > > ./me[0x41b791]
> > > ./me[0x41bd4b]
> > > ./me[0x41a8b6]
> > > ./me[0x43a8f4]
> > > ./me[0x43ae41]
> > > ./me[0x43aee0]
> > > /lib64/libc.so.6(__libc_start_main+0xf4)[0x396081da44]
> > > ./me[0x403a09]
> > > ======= Memory map: ========
> > > 00400000-00487000 r-xp 00000000 08:04
> > >
> > 328162 /home/enzo/Programmi/microemacs/me060909/src/me
> > > 00686000-0068f000 rw-p 00086000 08:04
> > >
> > 328162 /home/enzo/Programmi/microemacs/me060909/src/me
> > > 0068f000-00738000 rw-p 0068f000 00:00 0
> > > [heap]
> > > 3688000000-3688104000 r-xp 00000000 08:03
> > > 3106358 /usr/lib64/libX11.so.6.2.0
> > > 3688104000-3688304000 ---p 00104000 08:03
> > > 3106358 /usr/lib64/libX11.so.6.2.0
> > > 3688304000-368830b000 rw-p 00104000 08:03
> > > 3106358 /usr/lib64/libX11.so.6.2.0
> > > 3688800000-3688809000 r-xp 00000000 08:03
> > > 3127047 /usr/lib64/libXrender.so.1.3.0
> > > 3688809000-3688a08000 ---p 00009000 08:03
> > > 3127047 /usr/lib64/libXrender.so.1.3.0
> > > 3688a08000-3688a09000 rw-p 00008000 08:03
> > > 3127047 /usr/lib64/libXrender.so.1.3.0
> > > 3689000000-368900a000 r-xp 00000000 08:03
> > > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > > 368900a000-3689209000 ---p 0000a000 08:03
> > > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > > 3689209000-368920a000 rw-p 00009000 08:03
> > > 3127050 /usr/lib64/libXcursor.so.1.0.2
> > > 3689400000-3689410000 r-xp 00000000 08:03
> > > 3114633 /usr/lib64/libXpm.so.4.11.0
> > > 3689410000-3689610000 ---p 00010000 08:03
> > > 3114633 /usr/lib64/libXpm.so.4.11.0
> > > 3689610000-3689611000 rw-p 00010000 08:03
> > > 3114633 /usr/lib64/libXpm.so.4.11.0
> > > 3689800000-3689805000 r-xp 00000000 08:03
> > > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > > 3689805000-3689a04000 ---p 00005000 08:03
> > > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > > 3689a04000-3689a05000 rw-p 00004000 08:03
> > > 3127049 /usr/lib64/libXfixes.so.3.1.0
> > > 3960400000-396041a000 r-xp 00000000 08:03
> > > 1109786 /lib64/ld-2.5.so
> > > 3960619000-396061a000 r--p 00019000 08:03
> > > 1109786 /lib64/ld-2.5.so
> > > 396061a000-396061b000 rw-p 0001a000 08:03
> > > 1109786 /lib64/ld-2.5.so
> > > 3960800000-3960944000 r-xp 00000000 08:03
> > > 1109788 /lib64/libc-2.5.so
> > > 3960944000-3960b44000 ---p 00144000 08:03
> > > 1109788 /lib64/libc-2.5.so
> > > 3960b44000-3960b48000 r--p 00144000 08:03
> > > 1109788 /lib64/libc-2.5.so
> > > 3960b48000-3960b49000 rw-p 00148000 08:03
> > > 1109788 /lib64/libc-2.5.so
> > > 3960b49000-3960b4e000 rw-p 3960b49000 00:00 0
> > > 3961000000-3961003000 r-xp 00000000 08:03
> > > 1109804 /lib64/libdl-2.5.so
> > > 3961003000-3961202000 ---p 00003000 08:03
> > > 1109804 /lib64/libdl-2.5.so
> > > 3961202000-3961203000 r--p 00002000 08:03
> > > 1109804 /lib64/libdl-2.5.so
> > > 3961203000-3961204000 rw-p 00003000 08:03
> > > 1109804 /lib64/libdl-2.5.so
> > > 3961c00000-3961c0d000 r-xp 00000000 08:03
> > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > > 3961c0d000-3961e0c000 ---p 0000d000 08:03
> > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > > 3961e0c000-3961e0d000 rw-p 0000c000 08:03
> > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
> > > 3962400000-3962402000 r-xp 00000000 08:03
> > > 3125619 /usr/lib64/libXau.so.6.0.0
> > > 3962402000-3962601000 ---p 00002000 08:03
> > > 3125619 /usr/lib64/libXau.so.6.0.0
> > > 3962601000-3962602Aborted
> > >
> > > Ciao.
> > >
> > > Vincenzo
> > >
> > >
> > >
> > > --- In jasspa@yahoogroups.com
<mailto:jasspa%40yahoogroups.com>, Jon
> > Green <jon@> wrote:
> > > >
> > > > Thomas Hundt wrote:
> > > > > FYI It's working for me (SuSE 32-bit) and it's been very
> > stable
> > > over the
> > > > > past few years. What versions are you using?
> > > > >
> > > > > One thing I'd ask is, when you hit F10 to bring up the
file
> > > browser,
> > > > > does it recognize the symbolic links? (It should display
for
> > > example
> > > > > "HackSym/ -> Hack" for a link created using 'ln -s Hack
> > > HackSym'.)
> > > > >
> > > > > How far does it get when it crashes? When you click on (or
> > hit
> > > Return
> > > > > on) one of these entries, it says at the
bottom, "[Evaluating
> > > <item>]".
> > > > > It also changes the directory tree display on the left to
> > show
> > > the
> > > > > directories in the selected dir. And it changes the pane
on
> > the
> > > right
> > > > > to show the directories and files.
> > > > >
> > > > > -Th
> > > > >
> > > >
> > > > Good point, I wonder if there is an incompatibility with the
> > > linked
> > > > glibc.so? Maybe need to build from source to correct the
> > problem.
> > > The
> > > > current version is distributed with Gentoo and there do not
seem
> > > to be
> > > > any problems with Linux.
> > > >
> > > > Strongly suggest a source re-build and see how it goes on
your
> > > system.
> > > >
> > > > I was going to try building this on CentOs 5.0 to see what
> > > happens -
> > > > will do this later in the week.
> > > >
> > > > Jon.
> > > >
> > >
> >
> >
>

hkjava.emf   ~line 184

add a comma (,) to second character set to correctly highlight

     @see Foo#bar(wiz,wuz)

hilight .hilight.pjavadoc 0x80 "[#a-zA-Z][\\.#a-zA-Z0-9(),]*"
.hilight.javadoc .scheme.prepro


cheers
-- bryan

Hello all,

I recently observed a boog with the Dir Files - Toolbar. If you click
on the filename ME creates a new file with a leading number like "54
comment.emf" taken from the Dir Files listing. The correct filename
would be without the leading number. Furthermore the directory listing
seems to disappear if clicking on the "." and ".." entries. I was
hunting trought the tool*.emf files for trying to fix this. But I did
not find the region where the logic for this toolbar-stuff was sitting.

Tested Platforms: Win32 and Linux64

Any chance to fix this ?

regards,
Detlef

---

From: jasspa@yahoogroups.com [mailto:jasspa@yahoogroups.com] On Behalf Of Dr. Detlef Groth
Sent: 27 June 2007 10:51
To: jasspa@yahoogroups.com
Subject: [jasspa] Dir Files - Toolbar Bug

Hello all,

I recently observed a boog with the Dir Files - Toolbar. If you click
on the filename ME creates a new file with a leading number like "54
comment.emf" taken from the Dir Files listing. The correct filename
would be without the leading number. Furthermore the directory listing
seems to disappear if clicking on the "." and ".." entries. I was
hunting trought the tool*.emf files for trying to fix this. But I did
not find the region where the logic for this toolbar-stuff was sitting.

Tested Platforms: Win32 and Linux64

Any chance to fix this ?

regards,
Detlef

This sort of an rtfm-question, but...

?what? is the correct syntax for invoking grep on a buffer,
and piping it into another (preferably on-the-fly-one)?

Similarly for 'sort' (with args); uniq etc. I must be doing something
wrong, 'cause no dice.

Soon frustrated-no-mo' i-hope

Ian

this post <http://tech.groups.yahoo.com/group/jasspa/message/2272>

Hello,

I recently played a little bit with eclipse and it's Perl-EPIC plugin.
After each file save, the errors on the perl-file are underlined using
"perl -cw <filename>"  command -cw checks file and warns without
executing it. I tried to implement this feature for MicroEmacs as well
and came up with the following solution:


  define-macro perl-check
     set-alpha-mark "\x81"
     set-variable #l0 $buffer-bname
     pipe-shell-command &cat &cat "perl -cw \"" $buffer-fname "\""
     find-buffer "*command*"
     beginning-of-buffer
     set-variable #l1 "|"
     ; search all errors with the line string
     !force search-forward " line "
     !while $status
         forward-char
         backward-char
         set-mark
         forward-word
         exchange-point-and-mark
         copy-region
         ; TODO need to use restore the kill buffer
         !if &xse @y "\\d+"
             set-variable #l1 &cat &cat #l1 @y "|"

         !endif
         -1 yank
         !force search-forward " line "
     !done
     set-variable #l1 &cat #l1 "-1|"
     ; TODO need to avoid to open an other buffer-window
     find-buffer #l0
     set-variable #l2 1
     set-variable #l3 &lget #l1 #l2
     beginning-of-buffer
     ; remove all line hilighting
     !repeat
         ; Protect folded lines.
         !if ¬ &or &equ $line-scheme .scheme.fold-close &equ \
$line-scheme .scheme.fold-open
             set-variable $line-scheme -1
         !endif
         !force forward-line
     !until ¬ $status
     !if &great &len #l1 4
         ;        set-variable $debug 2
         !repeat
             beginning-of-buffer
             set-variable #l3 &sub #l3 1
             #l3 forward-line
             set-variable $line-scheme 9
             set-variable #l2 &add #l2 1
             set-variable #l3 &lget #l1 #l2
         !until &equal #l3 "-1"
         ml-write &cat "Errors on line(s):" &rep #l1 "-1|" ""
     !else
         ; TODO need to grab the status message currently in the
         ; message line and to combine it with our message
         ml-write "Syntax Ok"
     !endif
     screen-update
     goto-alpha-mark "\x81"
!emacro
  define-macro perl-save
     save-buffer
     -2000 command-wait
     perl-check
  !emacro

  buffer-bind-key perl-check "C-x C-k"

  buffer-bind-key perl-save "C-x C-s"

There are only two problems currently with this approach. Each time a
new window is opened for the current perl-buffer. And it would be nice
to implement a mouseover or similar on a colored line which should
give the the error-message on with ml-write. Is such a mouseover
possible for colored lines ?

regards,
Detlef

Ian wrote:
> This sort of an rtfm-question, but...
>
> ?what? is the correct syntax for invoking grep on a buffer,
> and piping it into another (preferably on-the-fly-one)?

If you really do want to run a shell command on the actual contents of a
buffer from the command line then use

filter-buffer "<command line with stdin/stdout options>"

I do think that this is actually what you want to do.

For grep <files> then use "M-x grep" the variable "%grep-com" is the
standard options.

The command "M-x uniq" and "M-x sort" work between point and mark and
are buffer equivalents of the standard UNIX commands.

For standard command line stuff then simply use "ipipe-shell-command"
and add the appropriate command line, the output is left in a '*'
temporary buffer.

>
> Similarly for 'sort' (with args); uniq etc. I must be doing something
> wrong, 'cause no dice.
>
> Soon frustrated-no-mo' i-hope

Sorry for the late response - not been around.

Hope that helps.
Jon.