bug#3438: emacs 23.0.9{,3,4} dired mode bug(?)

bug#3438: emacs 23.0.9{,3,4} dired mode bug(?)

[ishikawa]

Hi,

Thank you for making the great package available for pre-release testing.

While I began experimenting with this alpha/beta version,
I noticed a couple of lisp .elc files were not
correctly read, but I fixed them by
byte-recompile-directory.

After a day's use, I found a deeper problem with "dired" mode.

So I am reporting it here.

It is both in 23.0.93 which I initially tried, and
23.0.94 (confirmed today).

TIA.

========================================
A dired mode bug?
----------------------------------------
emacs-version : "23.0.93.1"
emacs-version : "23.0.94.1"  Both versions suffer from the same problem.


UNEXPECTED SYMPTOM:

In dired mode, when the cursor is near the beginning of a very long filename
(as in near the
"AaAaAa..." below ,
I can't move down to the next file by "n" or "cursor down" key anymore(!).

(Note that the folding of the long file name on the screen is such
that the said filename line is folded onto the next line. See
below. The space above the next filename "addition" is empty when
viewd with an X terminal of 100 characters wide.  Even if the width is
smaller (say, 80 chars) and "...ccccc" near the end comes above the
next file name "addition", the symptom is the same.).

Excerpt from a dired mode buffer: I am now on the line with "AaAaAa..." file.
Then I can't move the cursor down.

(darn. My current mailer refuses to send out the
lines unmodified...) Please not that the
AaAaAa... line below ought to follow 15:48 on the preceding line,
bbb... line ought to follow 15:49 on the preceding line, etc.
I hope you get the idea, though.)


  ....
  drwxr-xr-x  2 ishikawa   ishikawa  4096 2009-06-01 16:05 .
  drwxrwxrwx 62 cidellnote ishikawa 20480 2009-06-01 16:05 ..
  -rw-r--r--  1 ishikawa   ishikawa     5 2009-06-01 15:48
AaAaAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbccccccccccccccccccccccccccc
  -rw-r--r--  1 ishikawa   ishikawa     9 2009-06-01 16:04 addition
  -rw-r--r--  1 ishikawa   ishikawa     4 2009-06-01 15:49
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
  -rw-r--r--  1 ishikawa   ishikawa     4 2009-06-01 15:49
cccccccccccccccccccccccccccccccccccccccccccccc
  ....



EXPECTED BEHAVIOR:

I should be able to move down to the next filename line by
the cursor/mark by "n", "cursor down", or C-n.


ADDITIONAL NOTE:

I found that to my surprise that if my cursor is at the end of "AaAaAa"
that is the 6th character position, "n" or "cursor down" key moves the
cursor (mark) to the first "A" of the filename!

As I noted once I get there, cursor can't be moved down by "n" or "cursor
down" key (or control-n for that matter) any more.

I can move to the next line with "addition" filename, by going to the
end of the long filename by "C-e" and then further does the "c-f" to
the beginning of the next line (-rw-r--r--), but this is not what
dired designer had in mind, I think.

Going upward from the file name "addtion" in the above example
works fine as expected.

COMMENT/SUGGESTIONS:

Now, I suspect that this is due to the following change quoted from
etc/NEWS.

>* Editing Changes in Emacs 23.1
>
>+++
>** The C-n and C-p line-motion commands now move by screen lines,
>taking continued lines and variable-width characters into account.
>Setting `line-move-visual' to nil reverts this to the previous
>behavior (motion by logical lines based on buffer contents alone).

But if so, I think dired-mode should make a buffer-local version of
this variable (local to dired buffer) and set it to nil, IMHO.

This is because the way the cursor is supposed to move in dired
mode. The default cursor movement behavior of dired mode in 23.0.94
is broken, IMHO.

For the testing, I simply set this variable using
M-M-: (setq line-move-visual nil) [RETURN]

As I half expected, I found that the change of the variable restores
the expected behavior.  But this again changes the behavior everywhere
which I think the developers of 23.x version didn't intend. (Or
otherwise, the default C-N behavior would not be that of the 23.0.94).
Oh well.

[end of memo]

bug#3455: A solution for a problem with TAMAGO (egg) package for I18N input under emacs 23

[ishikawa]

Hi,

Thank you for making the great package available.

I have been testing emacs 23.0.94 for the last couple of days.

I am reporting a problem with an elisp package, TAMAGO, and a fix for it for
wider dissemination of the patch available for it.

I wish the information about the problem and the readily available fix is
incorporated into etc/NEWS file.

Backgrond:

With emacs 23.0.94, I noticed a problem with an elisp package called TAMAGO
(egg in Japanese) for I18N input.
I use it mostly for Japanese input.
With the widely available TAMAGO 4.0.6 distribution, which I use,
I can't input Japanese any more using emacs 23.0.94.

This is fixed by a patch posted a couple of years ago (in 2007) on
a mailing list which I found out yesterday.

The reported problem here is with this package, namely TAMAGO(egg), not
emacs 23.0.xx per se. But when I searched for the information about the
problem, the information is rather scarce. I found out some early Japanese
would-be testers of 23.0.xx reverted to emacs 22 version since they could
not use Japanese input any more using tamago(egg) package.

Given that there are many emacs users in Japan, and old timers like me seem
to use TAMAGO(egg) for Japanese input,
you might want to put the following info in etc/NEWS
to notify the potential problem and to avoid the extraneous
bug reports or questions.

I am afraid that the TAMAGO mailing list is not widely read these days.
And as far as I can tell, Tamago 4.0.6 seems to be the up-to-date version
that is made available to public. With the official release of emacs 23.1,
Mr. Handa et al may release the updated TAMAGO, but for now, we need the patch.

===========================
Problem with an tamago(egg) elisp package for I18N input

With emacs 23, there are changes in I18N character handling and
the changes break tamago(egg) Japanese input.

The problem is that when a user loads TAMAGO package, and sets it up so that
emacs will talk to Wnn input server, and tries to
input Japanese, the backend reports that (input) candidate  list
could not be created.
(The error appears in Japanese message. The above is my translation.)

Fix:

We should apply the patch reported in the following mailing list article
and (byte-) recompile egg-com.el using emacs 23.xx.

The following article is written in Japanese.

http://www.m17n.org/mlarchive/mule-ja/200703/msg00018.html

(Yes, it was posted more than two years ago.)

Caveat:

The fix modifies the egg-com.el file to use the new I18N function available
in emacs 23.xx only, and not available in emacs 22. So once the user
re-compile egg-com.el after applying the above patch,
the elc files can't be used for emacs 22 even if you decide to
byte-recompile the files using emacs22.

BTW, I am sure that TAMAGO needs
separate patch for each language it supports. Japanese input is taken care
of by the above patch.I wonder what changes are required for other languages
such as Korean
supported by TAMAGO package. But the change in the Japanese input patch
seemsto be rather straight-forward and so similar patches for other
languages can be written, I suppose.


That is all.

Thank you again for the great package.

Happy Hacking,
CI

bug#3455: A solution for a problem with TAMAGO (egg) package for I18N input under emacs 23

[Lars Magne Ingebrigtsen]

ishikawa <ishikawa@yk.rim.or.jp> writes:

> I am afraid that the TAMAGO mailing list is not widely read these days.
> And as far as I can tell, Tamago 4.0.6 seems to be the up-to-date version
> that is made available to public. With the official release of emacs 23.1,
> Mr. Handa et al may release the updated TAMAGO, but for now, we need the patch.
>
> ===========================
> Problem with an tamago(egg) elisp package for I18N input
>
> With emacs 23, there are changes in I18N character handling and
> the changes break tamago(egg) Japanese input.
>
> The problem is that when a user loads TAMAGO package, and sets it up so that
> emacs will talk to Wnn input server, and tries to
> input Japanese, the backend reports that (input) candidate  list
> could not be created.
> (The error appears in Japanese message. The above is my translation.)

This was reported two years ago, and I can't see that anything much
was done with it.  It doesn't seem like a bug in Emacs, though, so I'm
closing the report.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

bug#3455: A solution for a problem with TAMAGO (egg) package for I18N input under emacs 23

[ISHIKAWA,chiaki]

Dear Lars Magne Ingebrigtsen,

Thank you for your post.

I agree that it is not a bug in Emacs per se.

If the bug report remains in the bugzilla, and still could be searched,
the main purpose of the original bug report is fulfilled.
People who got bitten with the bug can search the bugzilla and find the
solution.

Too bad, I am not familiar with the innards of the handling of
multibyte character code sets anymore and so I can offer
a reasonable patch myself.

But thank you again for your attention on the
unclosed bugs in the bug report database.

Happy Hacking!

Sincerely,
Chiaki Ishikawa

(2011/09/17 14:57), Lars Magne Ingebrigtsen wrote:
> ishikawa<ishikawa@yk.rim.or.jp>  writes:
> 
>> I am afraid that the TAMAGO mailing list is not widely read these days.
>> And as far as I can tell, Tamago 4.0.6 seems to be the up-to-date version
>> that is made available to public. With the official release of emacs 23.1,
>> Mr. Handa et al may release the updated TAMAGO, but for now, we need the patch.
>>
>> ===========================
>> Problem with an tamago(egg) elisp package for I18N input
>>
>> With emacs 23, there are changes in I18N character handling and
>> the changes break tamago(egg) Japanese input.
>>
>> The problem is that when a user loads TAMAGO package, and sets it up so that
>> emacs will talk to Wnn input server, and tries to
>> input Japanese, the backend reports that (input) candidate  list
>> could not be created.
>> (The error appears in Japanese message. The above is my translation.)
> 
> This was reported two years ago, and I can't see that anything much
> was done with it.  It doesn't seem like a bug in Emacs, though, so I'm
> closing the report.
> 

bug#3455: A solution for a problem with TAMAGO (egg) package for I18N input under emacs 23

[Lars Magne Ingebrigtsen]

"ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp> writes:

> If the bug report remains in the bugzilla, and still could be searched,
> the main purpose of the original bug report is fulfilled.
> People who got bitten with the bug can search the bugzilla and find the
> solution.

The bugs remain in the bug database even if they are closed, and can
still be searched.  And are still visible via Google searches.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

bug#3438: marked as done (emacs 23.0.9{,3,4} dired mode bug(?))

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]


Your message dated Thu, 18 Jun 2009 15:29:42 -0400
with message-id <3k63etl4rd.fsf@fencepost.gnu.org>
and subject line Re: It was a configuration problem (re: (emacs 23.0.9{,3,4} dired mode bug(?)))
has caused the Emacs bug report #3438,
regarding emacs 23.0.9{,3,4} dired mode bug(?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3438: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3438
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 6868 bytes --]

From: ishikawa <chiaki.ishikawa@ubin.jp>
To: emacs-pretest-bug@gnu.org
Cc: ISHIKAWA Chiaki <chiaki.ishikawa@ubin.jp>
Subject: emacs 23.0.9{,3,4} dired mode bug(?)
Date: Mon, 01 Jun 2009 16:36:52 +0900
Message-ID: <4A238514.1010503@ubin.jp>

Hi,

Thank you for making the great package available for pre-release testing.

While I began experimenting with this alpha/beta version,
I noticed a couple of lisp .elc files were not
correctly read, but I fixed them by
byte-recompile-directory.

After a day's use, I found a deeper problem with "dired" mode.

So I am reporting it here.

It is both in 23.0.93 which I initially tried, and
23.0.94 (confirmed today).

TIA.

========================================
A dired mode bug?
----------------------------------------
emacs-version : "23.0.93.1"
emacs-version : "23.0.94.1"  Both versions suffer from the same problem.


UNEXPECTED SYMPTOM:

In dired mode, when the cursor is near the beginning of a very long filename
(as in near the
"AaAaAa..." below ,
I can't move down to the next file by "n" or "cursor down" key anymore(!).

(Note that the folding of the long file name on the screen is such
that the said filename line is folded onto the next line. See
below. The space above the next filename "addition" is empty when
viewd with an X terminal of 100 characters wide.  Even if the width is
smaller (say, 80 chars) and "...ccccc" near the end comes above the
next file name "addition", the symptom is the same.).

Excerpt from a dired mode buffer: I am now on the line with "AaAaAa..." file.
Then I can't move the cursor down.

(darn. My current mailer refuses to send out the
lines unmodified...) Please not that the
AaAaAa... line below ought to follow 15:48 on the preceding line,
bbb... line ought to follow 15:49 on the preceding line, etc.
I hope you get the idea, though.)


  ....
  drwxr-xr-x  2 ishikawa   ishikawa  4096 2009-06-01 16:05 .
  drwxrwxrwx 62 cidellnote ishikawa 20480 2009-06-01 16:05 ..
  -rw-r--r--  1 ishikawa   ishikawa     5 2009-06-01 15:48
AaAaAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbccccccccccccccccccccccccccc
  -rw-r--r--  1 ishikawa   ishikawa     9 2009-06-01 16:04 addition
  -rw-r--r--  1 ishikawa   ishikawa     4 2009-06-01 15:49
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
  -rw-r--r--  1 ishikawa   ishikawa     4 2009-06-01 15:49
cccccccccccccccccccccccccccccccccccccccccccccc
  ....



EXPECTED BEHAVIOR:

I should be able to move down to the next filename line by
the cursor/mark by "n", "cursor down", or C-n.


ADDITIONAL NOTE:

I found that to my surprise that if my cursor is at the end of "AaAaAa"
that is the 6th character position, "n" or "cursor down" key moves the
cursor (mark) to the first "A" of the filename!

As I noted once I get there, cursor can't be moved down by "n" or "cursor
down" key (or control-n for that matter) any more.

I can move to the next line with "addition" filename, by going to the
end of the long filename by "C-e" and then further does the "c-f" to
the beginning of the next line (-rw-r--r--), but this is not what
dired designer had in mind, I think.

Going upward from the file name "addtion" in the above example
works fine as expected.

COMMENT/SUGGESTIONS:

Now, I suspect that this is due to the following change quoted from
etc/NEWS.

>* Editing Changes in Emacs 23.1
>
>+++
>** The C-n and C-p line-motion commands now move by screen lines,
>taking continued lines and variable-width characters into account.
>Setting `line-move-visual' to nil reverts this to the previous
>behavior (motion by logical lines based on buffer contents alone).

But if so, I think dired-mode should make a buffer-local version of
this variable (local to dired buffer) and set it to nil, IMHO.

This is because the way the cursor is supposed to move in dired
mode. The default cursor movement behavior of dired mode in 23.0.94
is broken, IMHO.

For the testing, I simply set this variable using
M-M-: (setq line-move-visual nil) [RETURN]

As I half expected, I found that the change of the variable restores
the expected behavior.  But this again changes the behavior everywhere
which I think the developers of 23.x version didn't intend. (Or
otherwise, the default C-N behavior would not be that of the 23.0.94).
Oh well.

[end of memo]




[-- Attachment #3: Type: message/rfc822, Size: 1835 bytes --]

From: Glenn Morris <rgm+emacsbugs@gnu.org>
To: 3438-done@emacsbugs.donarmstrong.com
Subject: Re: It was a configuration problem (re: (emacs 23.0.9{,3,4} dired mode bug(?)))
Date: Thu, 18 Jun 2009 15:29:42 -0400
Message-ID: <3k63etl4rd.fsf@fencepost.gnu.org>

ishikawa wrote:

> After a false startup, I finally narrow down the problem to
> my hastily configured testing environment.
[...]
> In my .emacs file, I explicitly set the load-path to those of GNU
> emacs 22.2 lisp directory.


Thanks for letting us know. Closing this bug.