New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In some cases, not all files are displayed when using '-s' #205

Closed
andy5995 opened this Issue Nov 21, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@andy5995
Copy link
Member

andy5995 commented Nov 21, 2018

Noticed today that when viewing the list of files (when -s is used), that the list is incomplete. It only happens on one of my 3 waster folders. There are no gaps but the list stops after some files that begin with the letter "c".

@andy5995 andy5995 added this to the v0.4.06 milestone Nov 21, 2018

@andy5995 andy5995 self-assigned this Nov 28, 2018

@andy5995

This comment has been minimized.

Copy link
Member Author

andy5995 commented Nov 28, 2018

After some debugging, I found that a filename containing the character (146 on the extended ASCII chart) will cause this problem.

For example, if there is a file called custer’s last stand, at the menu selection window, I would see

...
carp
copying
culvert

and the listing would be ended. I can still scroll up and back down, and do everything as normal. I can quit the program and get a "0" for a return code.

I asked about it on LQ: https://www.linuxquestions.org/questions/showthread.php?p=5931334#post5931334

@andy5995 andy5995 closed this in 79a30c0 Nov 29, 2018

@andy5995 andy5995 reopened this Nov 29, 2018

andy5995 added a commit that referenced this issue Nov 29, 2018

Revert "enabled ncursesw wide-character support"
This reverts commit 79a30c0.

reopens #205
closes #206
@andy5995

This comment has been minimized.

Copy link
Member Author

andy5995 commented Nov 29, 2018

I guess what's needed for this to work right is to add a lot of tests to configure.ac to make sure the includes can be found on every system. On OpenBSD they're in /usr/include

On Debian they are in /usr/include/ncursesw

God knows about all the systems and distros.

And on OpenBSD, pkg-config reports

mercury# pkg-config --cflags-only-I ncursesw                                   
Package ncursesw was not found in the pkg-config search path

Although they do exist

mercury# pkg-config --cflags-only-I ncursesw                                   
Package ncursesw was not found in the pkg-config search path
mercury# locate libncurses
/usr/lib/libncurses.a
/usr/lib/libncurses.so.14.0
/usr/lib/libncurses_p.a
/usr/lib/libncursesw.a
/usr/lib/libncursesw.so.14.0
/usr/lib/libncursesw_p.a

On Slackware, you only need the ncurses package, and the includes are in /usr/include/ncurses, on Debian, the libncurses5 package can be removed and replaced with libncursesw5-dev and then there's no /usr/include/ncurses directory, but there's a /usr/included/ncursesw directory.

@andy5995 andy5995 closed this in 87ba2d6 Nov 29, 2018

andy5995 added a commit that referenced this issue Dec 6, 2018

document bug #205
[skip ci]
@andy5995

This comment has been minimized.

Copy link
Member Author

andy5995 commented Dec 6, 2018

As far as I know, there aren't any real obstacles to building with wide-char ncurses support on Linux, BSD, or OSX, so I'll leave this closed for now. Documented at https://remove-to-waste.info/doxygen/html/bug.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment