You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's assume a file named asdf:1234. This is a valid filename on Linux (or, at least, if you're using ext/xfs/zfs/...), but micro fails to open it properly - micro asdf\:1234 opens file asdf, same with using quotes, or even without escaping the colon at all.
It appears that the problem only occurs when a filename contains numbers right after the colon. The issue doesn't occur with any other special characters.
Specifications
Commit hash: Unknown, Version 2.0.3 from Void's repo
OS: Void Linux
Terminal: sakura (bash)
The text was updated successfully, but these errors were encountered:
This is because the syntax file.txt:line is used for opening a file at a specific line number. I'll have to think about the best way to support an escape syntax.
Description of the problem or steps to reproduce
Let's assume a file named
asdf:1234
. This is a valid filename on Linux (or, at least, if you're using ext/xfs/zfs/...), but micro fails to open it properly -micro asdf\:1234
opens fileasdf
, same with using quotes, or even without escaping the colon at all.micro asdf:
->asdf:
micro asdf::
->asdf::
micro asdf:1234
->asdf
micro asdf::1234
->asdf:
micro asdf\ :\ 1234
->asdf : 1234
(good!)micro asdf\ :1234
->asdf
micro asdf\ :1234.txt
->asdf
It appears that the problem only occurs when a filename contains numbers right after the colon. The issue doesn't occur with any other special characters.
Specifications
Commit hash: Unknown, Version 2.0.3 from Void's repo
OS: Void Linux
Terminal: sakura (bash)
The text was updated successfully, but these errors were encountered: