On Sunday, 30 March 2014 at 05:12:35 UTC, Walter Bright wrote:
> On 3/29/2014 8:50 PM, Kenji Hara wrote:
>> I'll refuse to maintain error number feature.
>
> :-)

Well, I think would be a "nice plus". If we have it, "yay!", but if we don't, I won't miss it.

Given Walter and Kenji's (and the rest of DMD's) limited manpower, I completely support their decision to not deploy this.

I think we should focus on improvements that *really* make a change.

On 2014-03-28 19:09, Walter Bright wrote:

> I've thought many times that an error message should be a clickable
> link. But until console displays support clickable text, it's just a
> fantasy.

There are other output forms, like IDE's and text editors that support links.

-- 
/Jacob Carlborg

On 2014-03-28 19:15, Walter Bright wrote:

> The ID's also make error messages look just plain ugly, as well as
> causing premature line wrapping, further uglifying the display.

There can of course be a flag that is required to be used to output the ID of the error message.

-- 
/Jacob Carlborg

On 2014-03-28 23:33, Kapps wrote:

> But without tool support I feel error codes aren't too useful, and in
> order to provide enough context to make tools useful you'd have to parse
> the error message in the first place which immediately makes it not
> practical and defeats the benefit of error codes.

We won't get tool support until there are ID's for error message. It's the chicken-and-egg problem.

-- 
/Jacob Carlborg

Am 28.03.2014 19:09, schrieb Walter Bright:
> On 3/28/2014 2:23 AM, monarch_dodra wrote:
>> Well, I'm just throwing that out there.
>
> I've thought many times that an error message should be a clickable
> link. But until console displays support clickable text, it's just a
> fantasy.

Actually on GNU/Linux systems many do.

On 3/30/2014 3:53 AM, monarch_dodra wrote:
> I think we should focus on improvements that *really* make a change.

Yup.

> I think we should focus on improvements that *really* make a change.

I've been missing from time to time the ability to sort my messages on *type* rather than file or line together with an IDE that present these in a tree (GUI) view where each warning message type node can be expanded or compressed. At least for big projects written in C/C++ where people have accidentally turned off important warning messages and then some other guy have found out that we need to turn it on (again) this would be a useful feature. This mainly because it's easier to fix a set of similar warnings at the same time as the solutions often are more closely related than warnings of different kind related solely by line locality.

Now, of course, D isn't C/C++ and D programs don't generated as my garbage output as C/C++ does when compiled...but still could become handy in very large D projects.

On 3/30/2014 4:03 AM, Jacob Carlborg wrote:
> We won't get tool support until there are ID's for error message.

I've pointed out how to do this without ID's several times.

On 3/30/2014 4:04 AM, Paulo Pinto wrote:
> Am 28.03.2014 19:09, schrieb Walter Bright:
>> On 3/28/2014 2:23 AM, monarch_dodra wrote:
>>> Well, I'm just throwing that out there.
>>
>> I've thought many times that an error message should be a clickable
>> link. But until console displays support clickable text, it's just a
>> fantasy.
>
> Actually on GNU/Linux systems many do.

I just tried it on Ubuntu and - you're right! Pretty awesome.

Can the URL be hidden behind text, like you'd do with html:

 <a href="dconf.org">D Conf!</a>

so the user sees the text rather than the link?

On Sunday, 30 March 2014 at 19:23:43 UTC, Walter Bright wrote:
> On 3/30/2014 4:04 AM, Paulo Pinto wrote:
>> Am 28.03.2014 19:09, schrieb Walter Bright:
>>> On 3/28/2014 2:23 AM, monarch_dodra wrote:
>>>> Well, I'm just throwing that out there.
>>>
>>> I've thought many times that an error message should be a clickable
>>> link. But until console displays support clickable text, it's just a
>>> fantasy.
>>
>> Actually on GNU/Linux systems many do.
>
> I just tried it on Ubuntu and - you're right! Pretty awesome.
>
> Can the URL be hidden behind text, like you'd do with html:
>
>  <a href="dconf.org">D Conf!</a>
>
> so the user sees the text rather than the link?

You can't do that, but you can output the URL and let the
terminal figure out that it should make it clickable at least,
which is what you just tried.