Hi,

My editor of choice is emacs (the version I got with Red Hat 9.0 which has a number of features that make it more like xemacs that I had when I ran SuSE 7.2 - maybe it is xemacs). The auto-indentation works great with C code, but is simply wrong when I edit php script. After the 1st 'if' statement, the indentation remains. For the subsequent few 'if's and 'foreach's the code that should be further indented isn't.

I have downloaded and installed php-mode 1.2.0 from SourceForge to no avail. Same problem.

I set the "TAB" key to self-insert-command to try to do my own indentation. But emacs would still auto-indent (wrongly) on typing characters like '('.

The only way I could stop emacs from auto-indenting was to remove php-mode altogether. This is not what I want as I want the syntax highlighting. In fact, I want auto-indenting because manually indenting can be so time-consuming, especially if you change the structure of your code. I just want it to work properly.

I resorted to vi. However, as well as having to manually indent, moving between buffers in vi is not nearly as quick and convenient as with emacs.

Does anyone know of an emacs lisp file for php mode that works properly, or another good editor.

TIA,

Lost Johnny

I've started using Kate recently and it has worked well for me.

Thanks,

My windows manager is Gnome, so I don't think I'll be able to use Kate, not easily at least, unless anyone knows better.

Lost Johnny

Further to my original message, I've found that the auto-indent works fine for function definitions. It's the code that's outside of any function that's not indenting properly.

I've found that PHP code that is outside of any function can be enclosed by a pair of braces. The script runs the same, but the emacs editor will indent properly between a pair of braces, while it will not properly indent code that is not between braces.

Graham

Bluefish will probably work well in GNOME.

Thanks for the info on alternative editors available.

Now that I've found the work-around of enclosing the code in braces I'll get on with what I know for now and maybe re-visit the idea of switching software if another issue comes up.

Cheers,

Graham