From: Dan D <va...@ms...> - 2000-04-26 20:56:34
|
I just got jEdit 2.4.2, and on running it, I noticed that one of the modes that I made for my personal use wasn't working anymore. I loaded it up in a buffer and started comparing it with the newest modes. I fixed a couple things that looked like errors in my mode, and loaded jEdit up again. No dice. I looked in the activity log, and it looks as if it isn't even trying to load up the mode. I have it in the proper directory and everything, but when I look at the messages when it's loading files, it just skips right over mine. I tried deleting the mode-cache file from the jedit home directory, that didn't work (I don't know why it would, but hey...). I do have a copy of jEdit 2.4pre5 installed, so I ran that, and it recognized the file. Just to check, I loaded up 2.4.2 again. Still nothing. I can't figure out what's going wrong. I looked in the X-mode documentation, but it seems to have been written quite some time ago, and is out of date. Any idea what's going on? Thanks in advance. ---------- Message To Spammers -- Game Over! Get spam-free email at http://www.MsgTo.com |
From: Eduardo I. I. <it...@eu...> - 2000-04-26 22:00:52
|
When a file is read-only, you can't modify it typing. But some commands like C-e C-b change the file. -- Eduardo Issao Ito <it...@eu...> Eurosoft Consultoria Ltda. <http://www.eurosoft.com.br> Rua Marina Saddi Haidar, 176 04650-050 - Sao Paulo - SP - Brasil Tel: +55 11 5524-8022 Fax: +55 11 5524-0408 |
From: Slava P. <sp...@gj...> - 2000-04-27 03:05:44
|
Eduardo Issao Ito wrote: > > When a file is read-only, you can't modify it typing. > But some commands like C-e C-b change the file. > Oops. The problem is that since read only protection is done at the text area, and not document level, commands that go at the document directly (eg, C+e C+b) must check the read only flag manually. I will go through all commands that make changes and ensure that they check this flag in 2.5pre1. Slava |
From: Slava P. <sp...@gj...> - 2000-04-27 03:05:51
|
Hi, Maybe you are placing the mode in jEdit 2.4pre5's mode directory by mistake? To find out where to place edit modes, load up jEdit 2.4.2 and invoke 'Utilities->Reload Edit Modes'. jEdit will then print a number of messages to the activity log as it rebuilds the mode cache. If that doesn't work, could you send me the mode file and your activity log? (you can save it to a file with Utilities->Activity Log->Save) Slava Dan D wrote: > > I just got jEdit 2.4.2, and on running it, I noticed that one of the modes that > I made for my personal use wasn't working anymore. I loaded it up in a buffer > and started comparing it with the newest modes. I fixed a couple things that > looked like errors in my mode, and loaded jEdit up again. No dice. I looked in > the activity log, and it looks as if it isn't even trying to load up the mode. > I have it in the proper directory and everything, but when I look at the > messages when it's loading files, it just skips right over mine. I tried > deleting the mode-cache file from the jedit home directory, that didn't work (I > don't know why it would, but hey...). > > I do have a copy of jEdit 2.4pre5 installed, so I ran that, and it recognized > the file. Just to check, I loaded up 2.4.2 again. Still nothing. I can't figure > out what's going wrong. I looked in the X-mode documentation, but it seems to > have been written quite some time ago, and is out of date. Any idea what's going > on? |