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

Line Breaks #4

Closed
Visiblink opened this issue Aug 12, 2023 · 2 comments
Closed

Line Breaks #4

Visiblink opened this issue Aug 12, 2023 · 2 comments

Comments

@Visiblink
Copy link

This is a strange issue. I use the gemini portal every day with the Lynx browser. Lynx doesn't have built-in Gemini support (I asked on their mailing list, but it's never been added) and the portal is a great way to keep using Lynx as an all-in-one browser.

Here's the issue: the gemini portal reproduces line breaks in gemtext faithfully when using it with Firefox. However, it produces a "wall of text" in Lynx.

Here's a site that demonstrates the issue really well: gemini://idiomdrottning.org/occams-turtles

image

Screenshot_2023-08-12_09-01-54

It's probably a Lynx issue, but if there's any way to fix it, I'd really appreciate it. Big thanks for this and pygopherd!

@michael-lazar
Copy link
Owner

Hi, I like to support Lynx and other niche web environments so thanks for posting this!

I'm using a CSS rule white-space: pre-wrap for the whitespace in gemini, and I don't think Lynx recognizes that rule (or any CSS at all?)

I just tried replacing the \n newlines with <br> tags and I think it looks like that solved it. I also had to go into my Lynx settings and disable COLLAPSE_BR_TAGS as described here:

https://unix.stackexchange.com/questions/170551/force-lynx-or-elinks-to-interpret-spaces-and-line-breaks

Screen Shot 2023-08-12 at 9 33 49 PM

@Visiblink
Copy link
Author

Thank you for making the change and looking into the Lynx setting. It worked perfectly!

For anyone reading this and using Debian, you need to go into /etc/lynx/lynx.cfg and uncomment COLLAPSE_BR_TAGS:TRUE and then change it to COLLAPSE_BR_TAGS:FALSE

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

No branches or pull requests

2 participants