Skip to content
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

'b' key issue in CalDAVClient #2

Closed
macosforgebot opened this issue Jul 30, 2008 · 7 comments
Closed

'b' key issue in CalDAVClient #2

macosforgebot opened this issue Jul 30, 2008 · 7 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Jul 30, 2008

vivien@… originally submitted this as ticket:301

  • Version: trunk

Hi,

Trying to use CalDAVClientLibrary on a Debian Lenny server, I noticed that the CalDAVClient shell did not allow to enter the 'b' letter.

This issue is quite annoying especially when your user id contains a 'b' :)

I found that this issue was reported on the CalendarServer-users mailing list in April 2008 [1]. Unfortunately this bug does not seem to have been fixed as I am running a fresh SVN checkout [2]

A patch [3] was proposed in reply to this email fixing this issue. Applying it solved this 'b' key issue problem.

Thanks, Vivien

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 14, 2008

@wsanchez originally submitted this as comment:1:⁠ticket:301

  • Priority changed from 5: Not set to 3: Important
  • Milestone set to Linux Port

I think this is a libedit vs. GNU readline issue.

This patch fixes it for readline while breaking libedit. If someone knows how to detect which is in use and do the right thing, that would be a more appropriate fix. In the meantime I will favor libedit despite readline's greater popularity, because readline's license is not a useable one for many of us.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 14, 2008

@wsanchez originally submitted this as comment:2:⁠ticket:301

  • Description modified
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Mar 24, 2009

macosforge@… originally submitted this as comment:3:⁠ticket:301


Thanks for the workaround. This indeed seems to be a known libedit/GNUreadline compatibility issue. http://trac.edgewall.org/ticket/6695 might be worth a look.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jan 24, 2013

@wsanchez originally submitted this as comment:5:⁠ticket:301

  • Milestone changed from Linux Port to Sooner
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jan 24, 2013

@wsanchez originally submitted this as comment:6:⁠ticket:301


The trick here is we need to code to figure out which binding is the correct one for the edit library in use…

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Mar 27, 2015

@wsanchez originally submitted this as comment:7:⁠ticket:301

  • Status changed from new to closed
  • Resolution set to Not to be fixed

Expiring old bugs with unknown state and impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.