RE: Character _ is a word constituent in JDE
Why stop there, why not get CamelCase mode...
http://www.hotdispatch.com/palm/view-ip-requester?ID=14317280
I use it with JDE and love it.
-Original Message-
From: Schewe, Jon (MN65) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 4:09 PM
To: 'Paul Kinnucan'
Cc: Schewe, Jon (MN65); ABAK Systèmes; [EMAIL PROTECTED]
Subject: RE: Character _ is a word constituent in JDE
What exactly do you expect to change if I run this
modify-syntax-entry?
Granted I'm using XEmacs, so I could be missing something
already, but I've
executed this and the only change I see is that M-b does what
the c-mode
thing when walking across variables with underscores in them.
Highlighting
looks exactly the same.
-Original Message-
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 3:59 PM
To: Paul Kinnucan
Cc: Schewe, Jon (MN65); ABAK Systèmes; [EMAIL PROTECTED]
Subject: RE: Character _ is a word constituent in JDE
Paul Kinnucan writes:
Schewe, Jon (MN65) writes:
Easy. Put this chunk of text in C mode and JDE mode
void method() {
int var_bar;
}
Now position the cursor on the ; and hit meta-b. In
c-mode the cursor jumps
to the b, in jde-mode it jumps to the v. I'm sure
there are other places
this comes into play, but this is the most annoying one
about JDE.
I think the jde-mode interpretation is correct and
preferable. The word is var_bar not bar. However, I will add
a customization variable to let people who care deeply about
this issue to choose the interpretation the JDE uses. Of
course, if you choose the c-mode interpretation, you will not
get syntax highlighting for names that begin with
underscores, which is, if I recall correctly, the original
reason cited by people who asked for this feature.
- Paul
I forgot to add that, meanwhile, you can reinstate the c-mode
interpretation by inserting the following form
(modify-syntax-entry ?_ )
into your jde-mode hook function.
- Paul
RE: Character _ is a word constituent in JDE
Schewe, Jon (MN65) writes:
-Original Message-
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 3:51 PM
To: Schewe, Jon (MN65)
Cc: 'Paul Kinnucan'; ABAK Systèmes; [EMAIL PROTECTED]
Subject: RE: Character _ is a word constituent in JDE
Schewe, Jon (MN65) writes:
Easy. Put this chunk of text in C mode and JDE mode
void method() {
int var_bar;
}
Now position the cursor on the ; and hit meta-b. In
c-mode the cursor jumps
to the b, in jde-mode it jumps to the v. I'm sure there
are other places
this comes into play, but this is the most annoying one about JDE.
I think the jde-mode interpretation is correct and
preferable. The word is var_bar not bar. However, I will add
a customization variable to let people who care deeply about
this issue to choose the interpretation the JDE uses. Of
course, if you choose the c-mode interpretation, you will not
get syntax highlighting for names that begin with
underscores, which is, if I recall correctly, the original
Why not? c-mode does it.
void method() {
int _bar;
int bar;
}
_bar is highlighted as a varible in c-mode.
Then I don't recall correctly. Anyway there was a good reason for doing this and it
had to do with names starting with underscores.
- Paul
RE: Character _ is a word constituent in JDE
Schewe, Jon (MN65) writes: What exactly do you expect to change if I run this modify-syntax-entry? Granted I'm using XEmacs, so I could be missing something already, but I've executed this and the only change I see is that M-b does what the c-mode thing when walking across variables with underscores in them. Highlighting looks exactly the same. I put this change in at the request of users who start field names with underscores. This was years ago. I don't recall the reason it was necessary but I assure you it WAS necessary and I'm not going to remove the default now nor am I goint to spend any further time on this issue. - Paul
Re: Character _ is a word constituent in JDE
Paul Kinnucan a écrit : However, I will add a customization variable to let people who care deeply about this issue to I am not sure there is a need for one more customization variable as we can always modify syntax in jde-mode-hook. If you think there are some reasons to not change the default, it would be enough to simply add an item in the doc about that. I don't want to waste your time. I asked about that because I didn't understood the comment in jde.el and I realize that I am not the only one. But it is not a very important topic. Thanks for your answers. -- Pascal Quesseveur, [EMAIL PROTECTED] ABAK Systèmes, ZI Le Rachat - BP 5 - 35890 LAILLE Tel: +33(0) 299.42.30.10, Fax: +33(0) 299.42.31.57
