Bug 1351056 - Multi-line prompt is not treated correctly in command line editing
Summary: Multi-line prompt is not treated correctly in command line editing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Kaspar // Dee'Kej
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-29 06:33 UTC by Kensuke IWAHASHI
Modified: 2016-07-20 17:48 UTC (History)
6 users (show)

Fixed In Version: tcsh-6.19.00-10.fc24
Clone Of:
Environment:
Last Closed: 2016-07-20 17:48:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch to fix the problem of determination of NLSClass (739 bytes, patch)
2016-07-04 02:25 UTC, Kensuke IWAHASHI
no flags Details | Diff

Description Kensuke IWAHASHI 2016-06-29 06:33:17 UTC
Description of problem:
After upgrading tcsh from tcsh-6.19.00-3.fc23.x86_64 to tcsh-6.19.00-9.fc24.x86_64, multi-line prompt is not treated correctly in command line editing.  I found the following patch might make the problem.
tcsh-6.19.00-007-fix-handling-of-invalid-unicode-characters.patch
But I do not know how to fix it.

Version-Release number of selected component (if applicable):
tcsh-6.19.00-9.fc24.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. cd ~
2. set prompt="%~\n%%"
3. ctrl-p, ctrl-u

Actual results:
~
%se

Expected results:
~
%

Comment 1 Kensuke IWAHASHI 2016-07-04 02:25:33 UTC
Created attachment 1175756 [details]
Patch to fix the problem of determination of NLSClass

This proposed patch determines whether a character is a control code at the first in NLSClassify().  Function NLSClassify() never returns NLSCLASS_NL, NLSCLASS_TAB and NLSCLASS_CTRL when drawPrompt flag is true unless this patch is applied.

Comment 2 David Kaspar // Dee'Kej 2016-07-04 10:11:50 UTC
Thank you for the patch, Kensuke.

Have you proposed this patch to upstream yet? If not, would you like to do it, or should I do it on your behalf? :)

Best regards,

Dee'Kej

Comment 3 Kensuke IWAHASHI 2016-07-04 23:28:50 UTC
I have not proposed it to upstream yet.
Would you please propose it on my befalf?

Best regards,
Kensuke IWAHASHI

Comment 4 David Kaspar // Dee'Kej 2016-07-08 15:23:43 UTC
Sure, no problem. I will do it. :)

Comment 5 David Kaspar // Dee'Kej 2016-07-15 10:47:05 UTC
So, as you have probably already noticed, I have contacted upstream:
http://mx.gw.com/pipermail/tcsh-bugs/2016-July/001071.html

Lets see what they have to say about this... :)

Comment 6 David Kaspar // Dee'Kej 2016-07-18 15:00:29 UTC
Upstream has accepted the patch, I have submitted it into git:
http://pkgs.fedoraproject.org/cgit/rpms/tcsh.git/commit/?id=ae5f8a98adbe

I will add the build into bodhi tomorrow, so you can test it. (I'm sorry, I have to leave work now.)

Comment 7 Fedora Update System 2016-07-19 13:20:07 UTC
tcsh-6.19.00-10.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e6666b3570

Comment 8 Kensuke IWAHASHI 2016-07-19 13:39:32 UTC
Thank you for fixing this problem.  It works fine.

Comment 9 David Kaspar // Dee'Kej 2016-07-19 14:13:09 UTC
If it (does not) works for you, please make an unpdate in Bodhi by adding +/-1 to karma. Once it has enough positive karma, it should be pushed from testing to stable automatically... ;)

Comment 10 Fedora Update System 2016-07-20 01:53:15 UTC
tcsh-6.19.00-10.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e6666b3570

Comment 11 Fedora Update System 2016-07-20 17:48:17 UTC
tcsh-6.19.00-10.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.