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.

Sign up for GitHub

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

Jump to bottom

__UNDEF__ vs. __undef__ #12

Open
dwhieb opened this issue Feb 3, 2021 · 2 comments
Open

__UNDEF__ vs. __undef__ #12

dwhieb opened this issue Feb 3, 2021 · 2 comments
Assignees
@dwhieb
Labels
bug Something isn't working

Comments

@dwhieb
Copy link

dwhieb commented Feb 3, 2021 •
edited
Loading

  • __UNDEF__ displays as [_empty_], which is the expected behavior.
  • __undef__ displays as a verbatim string, which is bad.
  • Test case: êkwa

Current Behavior:
image

Expected Behavior:
Should look like the [empty] cases in this image:
image
@dwhieb dwhieb added the bug Something isn't working label Feb 3, 2021
@dwhieb dwhieb mentioned this issue Feb 3, 2021
Closed
@dwhieb
Copy link
Author

dwhieb commented Feb 6, 2021 •
edited
Loading

This appears to have been resolved along with #10 in e89bdfa. Closing unless this issue arises again.

@dwhieb dwhieb closed this as completed Feb 6, 2021
@dwhieb dwhieb self-assigned this Feb 6, 2021
@dwhieb dwhieb reopened this Feb 9, 2021
@dwhieb
Copy link
Author

dwhieb commented Feb 9, 2021

Issue is still occurring in the Info Box.

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

@dwhieb dwhieb

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dwhieb