From: Javier Sedano <javier.sedano@gmail.com>
To: cygwin@cygwin.com
Subject: syntax highlighting on Joe
Date: Mon, 26 Jan 2009 19:56:00 -0000 [thread overview]
Message-ID: <497E07CC.3000700@gmail.com> (raw)
Hi friends,
I've been using cygwin for many years, but had never subscribed to this
list. Now, I have a strange behaviour, and hope you can help me.
I'm a fan of the Joe editor. I use it on xterm. Up to now, it had
always made syntax-higglighting out of the box. However, when I
installed it yesterday (from the latest version, using the mirror
cygwin.cict.fr) on a new computer, it did not.
It seems that the syntax file are not the problem, because (a) the jsf
files are there (see the log below); and (b) the autoindent for example
is working.
Any idea?
Since I am using it on xterm, it may be a problem related to cygwin/x.
Feel free to forward me to another list if you think that's a better
place for the question.
Thank you in advance,
jsedano@flint:~/prj> ls /usr/share/joe/syntax/
4gl.jsf csh.jsf joerc.jsf pascal.jsf sed.jsf troff.jsf
ada.jsf css.jsf lisp.jsf perl.jsf sh.jsf verilog.jsf
asm.jsf diff.jsf lua.jsf php.jsf skill.jsf vhdl.jsf
awk.jsf fortran.jsf m4.jsf ps.jsf sml.jsf xml.jsf
c.jsf haskell.jsf mail.jsf python.jsf sql.jsf
cobol.jsf html.jsf mason.jsf rexx.jsf tcl.jsf
conf.jsf java.jsf ocaml.jsf ruby.jsf tex.jsf
jsedano@flint:~/prj>
--
--
Javier Sedano
javier.sedano@gmail.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2009-01-26 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:56 Javier Sedano [this message]
2009-01-26 22:31 ` Javier Sedano
2009-01-27 5:29 ` Julio Emanuel
2009-01-27 6:17 ` Larry Hall (Cygwin)
2009-01-27 13:58 ` Julio Emanuel
2009-01-27 19:50 ` Javier Sedano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497E07CC.3000700@gmail.com \
--to=javier.sedano@gmail.com \
--cc=cygwin@cygwin.com \
/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).