unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@surf.glug.org>
Subject: #:keyword font locking for scheme.el
Date: Mon, 29 Sep 2003 02:12:06 +0200	[thread overview]
Message-ID: <E1A3le2-0003ot-00@surf.glug.org> (raw)

any objections to this change (patch below) to scheme.el?
it enables font locking for both

	:this-style

as well as

	#:this-style

keywords.  currently for the latter, the hash is left unfontified,
which i suppose could be aesthetically pleasing to some...

a related-elisp question: i notice imenu has a similar init string as
the one changed for `font-lock-defaults'.  should that be changed, too?

passing note: guile allows both styles to be recognized as keywords,
depending on an option that affects `read'.  because of lack of hash
fontification back when i was getting into scheme programming (when i
finally tried using emacs under X w/ hilit19, that is ;-), a lot of my
code avoided "#:key" to use ":key" because it was prettier.  silly
programmer.

thi


____________________________________________________
*** scheme.el.~1.45.~	Sun Sep  7 11:24:10 2003
--- scheme.el	Mon Sep 29 01:46:57 2003
***************
*** 165,171 ****
    (setq font-lock-defaults
          '((scheme-font-lock-keywords
             scheme-font-lock-keywords-1 scheme-font-lock-keywords-2)
!           nil t (("+-*/.<>=!?$%_&~^:" . "w")) beginning-of-defun
            (font-lock-mark-block-function . mark-defun)
            (font-lock-syntactic-face-function . lisp-font-lock-syntactic-face-function))))
  
--- 165,171 ----
    (setq font-lock-defaults
          '((scheme-font-lock-keywords
             scheme-font-lock-keywords-1 scheme-font-lock-keywords-2)
!           nil t (("+-*/.<>=!?$%_&~^:#" . "w")) beginning-of-defun
            (font-lock-mark-block-function . mark-defun)
            (font-lock-syntactic-face-function . lisp-font-lock-syntactic-face-function))))
  
***************
*** 337,344 ****
        ;; David Fox <fox@graphics.cs.nyu.edu> for SOS/STklos class specifiers.
        '("\\<<\\sw+>\\>" . font-lock-type-face)
        ;;
!       ;; Scheme `:' keywords as builtins.
!       '("\\<:\\sw+\\>" . font-lock-builtin-face)
        )))
    "Gaudy expressions to highlight in Scheme modes.")
  
--- 337,344 ----
        ;; David Fox <fox@graphics.cs.nyu.edu> for SOS/STklos class specifiers.
        '("\\<<\\sw+>\\>" . font-lock-type-face)
        ;;
!       ;; Scheme `:' and `#:' keywords as builtins.
!       '("\\<#*:\\sw+\\>" . font-lock-builtin-face)
        )))
    "Gaudy expressions to highlight in Scheme modes.")
  


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2003-09-29  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29  0:12 Thien-Thi Nguyen [this message]
2003-09-29  7:17 ` #:keyword font locking for scheme.el Neil Jerram
2003-09-29 12:13   ` Thien-Thi Nguyen
2003-09-29 23:19 ` Rob Browning

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/guile/

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

  git send-email \
    --in-reply-to=E1A3le2-0003ot-00@surf.glug.org \
    --to=ttn@surf.glug.org \
    --cc=ttn@glug.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).