Package: emacs21-el
Version: 21.4a-1
Severity: normal

allout.el does not work with some types of outline-header-prefix.
If I set outline-header-prefix, e.g., to "CCC_", outline-open-topic 
does not make right topic, shows strange behavior.

I found this error comes from set-outline-regexp.
There is a block as follows in definition of set-outline-regexp:

  ;; Produce the new outline-regexp:
  (setq outline-regexp (concat "\\(\\"
                               outline-header-prefix
                               "[ \t]*["
                               outline-bullets-string
                               "]\\)\\|\\"
                               outline-primary-bullet
                               "+\\|\^l"))

This definition should be replaced with as follows:

  ;; Produce the new outline-regexp:
  (setq outline-regexp (concat "\\("
                               (regexp-quote outline-header-prefix)
                               "[ \t]*["
                               outline-bullets-string
                               "]\\)\\|"
                               (regexp-quote outline-primary-bullet)
                               "+\\|\^l"))

I realized that this error also occurs if explicitly set "***_" to
outline-header-prefix.  This time outline-regexp's value is:
"\\(\\***_[     ]*[\\.:,;\\*\\+--=>(\\[{}&!\\?#%\"[EMAIL 
PROTECTED])\\|\\*+\\|\f".
The asterisk triplet is not expressed in the regular expression.
In this case asterisk need not to be triplet;  "*_", or "*******_"
work as well.  I do not think we expect these behavior.

SAITO Fuyuki, [EMAIL PROTECTED]


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP)

Versions of packages emacs21-el depends on:
ii  emacs21-common                21.4a-1    The GNU Emacs editor's shared, arc

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to