Cai Qian | 1 Jun 01:46 2006
Picon

Re: sh-script-mode

Hi,

On 5/29/06, Richard Stallman <rms <at> gnu.org> wrote:
>     3) Highlight for quote string
>     Highlight for quota string is a mess, when embed double or single
>     quota inside quota, such as,
>
>     echo "$(echo "hello 'world'")"
>
> I think the syntax mechanism is not powerful enough to understand that.
> Sorry.
>

I think it is necessary here to change the behaviour of syntax
highlight of quote string. For example,

echo "$(ls "Hello World"*)"

Two quote strings are valid and necessary here to protect spaces as
well as newlines. In addition, I don't think it is too hard to support
it. When the first " char looking for the end of " char, it needs to
skip " char inside $(...)

Qian
Martin J. Reed | 1 Jun 18:37 2006
Picon

regexp problem in ldap.el?

Hi,

I have had problems with ldap.el. It seems that the version shipped
(and latest CVS) matches erroneous lines in the grabbed output from
ldapsearch when SASL authentication is used. The problem may also
occur in other situations (I think it is a genuine bug). I have had to
apply the following diff (to ldap-1.11.2.10.el grabbed from CVS):

--------------------------->8-------------------------------------
diff -u ldap-1.11.2.10.el ldap-1.11.2.10-reed.el 
--- ldap-1.11.2.10.el   2006-06-01 17:05:40.000000000 +0100
+++ ldap-1.11.2.10-reed.el      2006-06-01 17:04:41.000000000 +0100
 <at>  <at>  -154,7 +154,7  <at>  <at> 
   :type '(string :tag "`ldapsearch' Program")
   :group 'ldap)

-(defcustom ldap-ldapsearch-args '("-LL" "-tt" "-x")
+(defcustom ldap-ldapsearch-args '("-LL" "-tt")
   "*A list of additional arguments to pass to `ldapsearch'."
   :type '(repeat :tag "`ldapsearch' Arguments"
                 (string :tag "Argument"))
 <at>  <at>  -555,7 +555,7  <at>  <at> 
          (setq arglist (nconc arglist (list (format "-z%s" sizelimit)))))
       (eval `(call-process ldap-ldapsearch-prog
                           nil
-                          `(,buf nil)
+                          buf
                           nil
                           , <at> arglist
                           , <at> ldap-ldapsearch-args
(Continue reading)

Hallvard B Furuseth | 1 Jun 21:49 2006
Picon
Picon

Re: regexp problem in ldap.el?

Martin J. Reed writes:
> diff -u ldap-1.11.2.10.el ldap-1.11.2.10-reed.el 
> --- ldap-1.11.2.10.el   2006-06-01 17:05:40.000000000 +0100
> +++ ldap-1.11.2.10-reed.el      2006-06-01 17:04:41.000000000 +0100
>  <at>  <at>  -154,7 +154,7  <at>  <at> 
>    :type '(string :tag "`ldapsearch' Program")
>    :group 'ldap)
>  
> -(defcustom ldap-ldapsearch-args '("-LL" "-tt" "-x")
> +(defcustom ldap-ldapsearch-args '("-LL" "-tt")
>    "*A list of additional arguments to pass to `ldapsearch'."

That one needs to be more complex.

With OpenLDAP ldapsearch, removing "-x" turns on SASL Bind (if it is
compiled in), and with SASL turned on you lose support for anonymous
connections.  For simple search operations, I think anonymous
connections are far more common than SASL-authenticated connections.
For that matter, plenty of server installations have not been set up
to support SASL, even when the implementation does support it.

I think -x is an OpenLDAPism though.  Solaris ldapsearch does not
understand -x, at least not on the SunOS 5.8 I just tried.  It does have
an '-M CRAM-MD5' option, which seems rather outdated:  When I tried -M
DIGEST-MD5 it reverted to anonymous Simple Bind.  And it talks about
RFC-1558 search filters, which is two LDAP RFC revisions out of date.

> The change of ldap-ldapsearch-args is probably not important (although
> do we want users to use the insecure unencrypted form by default?),

(Continue reading)

Dan Jacobson | 2 Jun 21:52 2006

diff should offer bully mode

(emacs-version"22.0.50.1") When one uses
  = runs the command dired-diff
      which is an interactive compiled Lisp function in `dired-aux.el'.
The half window given isn't big enough to see much diff output, at
least for me.
Instead of splitting the window in half, it be possible to have diff
  take over the whole window, like man's bully mode.
The problem must be in the inflexible
      (display-buffer buf)
in the diff function.
Dan Jacobson | 3 Jun 04:34 2006

what-cursor-position vs. Unicode

Today we shall discuss what-cursor-position when given an argument of ^U.
We see that it gives Unicode information:
  character: Z (90, #o132, #x5a, U+005A)
Except when you really need it:
  character: 丹 (107109, #o321145, #x1a265)
It should mention U+4E39.
emacs-version "22.0.50.1"
Dan Jacobson | 3 Jun 01:19 2006

dired-sort-toggle-or-edit: * vs. -R

dired-sort-toggle-or-edit: -R doesn't work on wildcard directories:
$ emacs -q
C-x d / e t c / r c * <return> C-u s R <return>
Nothing happens. -og works though.
(emacs 22.0.50.1)
Eli Zaretskii | 3 Jun 10:09 2006
Picon

Re: what-cursor-position vs. Unicode

> From: Dan Jacobson <jidanni <at> jidanni.org>
> Date: Sat, 03 Jun 2006 10:34:59 +0800
> Cc: handa <at> etl.go.jp
> 
> It should mention U+4E39.
> emacs-version "22.0.50.1"

It does for me, at least when reading your mail.

Perhaps you should send the original file (as a binary attachment), or
describe how you produced the character, if it wasn't from a file.

Also, please tell when was your Emacs resync'ed with CVS, and please
try looking at the character in "emacs -Q".
Kenichi Handa | 5 Jun 09:01 2006

Re: what-cursor-position vs. Unicode

In article <87irnjklv0.fsf <at> jidanni.org>, Dan Jacobson <jidanni <at> jidanni.org> writes:

> Today we shall discuss what-cursor-position when given an argument of ^U.
> We see that it gives Unicode information:
>   character: Z (90, #o132, #x5a, U+005A)
> Except when you really need it:
>   character: 丹 (107109, #o321145, #x1a265)
> It should mention U+4E39.
> emacs-version "22.0.50.1"

#x1a265 is a character of chinese-cns11643-1, and the
current Emacs doesn't support Unicode mapping for that
character set.

---
Kenichi Handa
handa <at> m17n.org
Werner LEMBERG | 5 Jun 10:22 2006
Picon

Re: what-cursor-position vs. Unicode


> #x1a265 is a character of chinese-cns11643-1, and the
> current Emacs doesn't support Unicode mapping for that
> character set.

Just wondering: Why not?

    Werner
Kenichi Handa | 5 Jun 13:07 2006

Re: what-cursor-position vs. Unicode

In article <20060605.102222.112830788.wl <at> gnu.org>, Werner LEMBERG <wl <at> gnu.org> writes:

>> #x1a265 is a character of chinese-cns11643-1, and the
>> current Emacs doesn't support Unicode mapping for that
>> character set.

> Just wondering: Why not?

Because no one has implemented it.  I myself want to avoid
spending a time on what becomes useless in the future.  In
addition, in the current Emacs code, adding something like
lisp/international/subst-cns.el leads to slower startup in
CJK locales, which I want to avoid.

But, if someone implement it and Richard agrees on including
it before the release, please go ahead.

---
Kenichi Handa
handa <at> m17n.org

Gmane