-
Notifications
You must be signed in to change notification settings - Fork 123
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
Markdown Link Converter: Change Location Style #2445
The head ref may contain hidden characters: "\u{1F517}"
Conversation
The previous style was created for some other editor. But I am okay with this change if it works better for you. |
Interesting. Do you remember the name of the editor? The location style
should be pretty much the standard format. For example, it is also the default style for error messages, if you compile some files with |
Yes, this was the reason. Isn't it better to keep it, then? |
Your version of
as default error style? At least seem to use
by default, according to the output of various build jobs. |
filename|line col 0| | ||
``` | ||
|
||
to show the location data for broken links. This has the advantage, that certain tools such as [TextMate](https://macromates.com) are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed: please write here that this is a default format for gcc, clang, ...
While the location style: filename|line col 0| is perfectly readable by a human, most applications prefer something like filename:line:0 . For example, in TextMate the second variant does produce clickable links, while the first style does not.
@@ -9,7 +9,7 @@ should be hard to use it in a wrong way. This tutorial gives an introduction for | |||
using the high-level API. | |||
|
|||
The API supports all CORBA Basic Data Types, except for `wchar`, as well as the `string` type | |||
(see also [Data Types](../high-level-api#data-types) below). | |||
(see also [Data Types](#data-types) below). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not work on the homepage (also not the previous version)
Thank you! Can you open an issue or PR for the broken links please? |
No description provided.