-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
[Bug] Viewer/Editor - comma or other punctuation mark at beginning of line #1197
Labels
Comments
@Andreas0602 can you report this behavior to https://github.com/bobbylight/RSyntaxTextArea ? |
done |
pskowronek
added a commit
to pskowronek/mucommander-for-pr
that referenced
this issue
May 27, 2024
ahadas
pushed a commit
that referenced
this issue
May 27, 2024
bumping to 3.4.0 doesn't fix the problem, unless @ahadas you had other intention - but personally I would keep it open to observe if/when bug on RSyntaxTextArea is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Description
When you view a txt file in the internal viewer or editor and line wrap is enabled, it can happen in an unfavorable case that a comma or other punctuation mark is at the beginning of a line. Similarly, it can happen that an opening parenthesis or a quotation mark is at the end of a line.
Steps to reproduce
see above
Expected behavior
For txt files, there should be no line break between a word and a directly following comma, period, semicolon, colon, hyphen etc. Also, there should be no line break between an opening parenthesis and a word.
Actual behavior
see above
Screenshots?
muCommander version
Version: 1.5.0
Build date: 2024/05/27
Build number: 8ae2283
Java version
Runtime version: 23-internal
VM name: OpenJDK 64-Bit Server VM
VM version: 23-internal-ahadas-0081ac197a656cdc0d88d5a5e2a0f399ee023654
VM vendor: Oracle Corporation
Operating System type and version
Name: Mac OS X
Version: 14.5
Architecture: aarch64
Relevant log output
No response
The text was updated successfully, but these errors were encountered: