[Bug] When a filename contains a colon and a number, the opened file may be incorrect.

[munich91]

For example, the directory contains the files:

a.txt
a.txt:1

msedit a.txt:1 will always open a.txt and goto line 1, open it from the menu same too.

Currently, the options for specifying rows and columns are optionally placed after the file name. It might be clearer and more user-friendly if these options were separated from the file name entirely. This would make the syntax more consistent and easier to read.

OS: Arch Linux

[lhecker]

Do you have an actual file with a colon in its name or is this more of a theoretical concern? The current design is rather intentional after all - it allows you to open msedit with an URI.

[munich91]

I don’t often encounter filenames containing colons; in my case, it mainly happens because my project’s log files are formatted this way.
If this is an intentional design choice, would it be possible—similar to how some libraries handle it—to allow escaping colons with a backslash? For example, like msedit "a.txt\:1" just open file "a.txt:1".
Personally, avoiding this situation is not difficult, but supporting such special cases could make the program more robust and flexible.