unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Andrea Venturoli <ml.diespammer@netfence.it>
To: help-gnu-emacs@gnu.org
Subject: Editing PHP/HTML and nxHTML
Date: Wed, 15 Jun 2016 10:54:07 +0200	[thread overview]
Message-ID: <njr53f$1r28$1@gioia.aioe.org> (raw)

Hello.

I'm in need to edit HTML code and mixed PHP/HTML code.
I'm not in for anything fancy: synthax highlighting, tags mismatch 
detection and proper indenting is enough for me.

I searched the web for the suggested best option and it seems nxHTML is 
highly backed.
However I'm getting tons of problems with it (see details at the end if 
you want)...
I think I've got the latest version (2.08), which seems quite old 
anyway. Is this still a supported package? Is it compatible with the 
latest emacs?

Any pointer on how to make it work or any suggestion for a replacement?

  bye & Thanks
	av.



Details

As soon as I start emacs on an HTML file I get the following warnings:
> Warning: `comment-use-global-state' is an obsolete variable (as of 24.4); use
>     `comment-use-syntax' instead.
> Warning: `font-lock-beginning-of-syntax-function' is an obsolete variable (as
>     of 23.3); use `syntax-begin-function' instead.
> Warning: `font-lock-syntactic-keywords' is an obsolete variable (as of 24.1);
>     use `syntax-propertize-function' instead.
> Warning: `comment-use-global-state' is an obsolete variable (as of 24.4); use
>     `comment-use-syntax' instead.
> Warning: `font-lock-beginning-of-syntax-function' is an obsolete variable (as
>     of 23.3); use `syntax-begin-function' instead.
> Warning: `font-lock-syntactic-keywords' is an obsolete variable (as of 24.1);
>     use `syntax-propertize-function' instead.
> Warning: `comment-use-global-state' is an obsolete variable (as of 24.4); use
>     `comment-use-syntax' instead.
> Warning: `font-lock-beginning-of-syntax-function' is an obsolete variable (as
>     of 23.3); use `syntax-begin-function' instead.
> Warning: `font-lock-syntactic-keywords' is an obsolete variable (as of 24.1);
>     use `syntax-propertize-function' instead.

I could live with these, but others come up every so often.

The bell is constantly ringing with some messages like "Wrong number of 
arguments..." or "Error running timer..." or a lot of others.

Indentation rarely works properly.

"ediff-buffers" or "ediff-revision" is a risk, since it won't work 
properly (deleting codes it shouldn't delete or adding some code where 
it should *replace* some code).

And I could go on...


             reply	other threads:[~2016-06-15  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  8:54 Andrea Venturoli [this message]
2016-06-15 17:05 ` Editing PHP/HTML and nxHTML Andreas Röhler
     [not found] ` <mailman.1548.1466010062.1216.help-gnu-emacs@gnu.org>
2016-06-15 18:18   ` Andrea Venturoli
2016-06-15 18:31 ` Dmitry Gutov
2016-06-16  9:55   ` Chris Van Dusen
2016-06-17 22:38     ` Stefan Monnier
2016-06-18 22:11       ` Chris Van Dusen
2016-06-18 22:36         ` Emanuel Berg
2016-06-19  0:12           ` John Mastro
2016-06-19  1:51             ` Emanuel Berg
2016-06-19 21:14         ` Stefan Monnier
     [not found]         ` <mailman.1824.1466370906.1216.help-gnu-emacs@gnu.org>
2016-06-20  1:10           ` Emanuel Berg
2016-06-20  3:33             ` Stefan Monnier
     [not found] ` <mailman.1555.1466015502.1216.help-gnu-emacs@gnu.org>
2017-01-25 11:39   ` Andrea Venturoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='njr53f$1r28$1@gioia.aioe.org' \
    --to=ml.diespammer@netfence.it \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).