On 16/04/2023 10:49 a.m., nos...@altfeld-im.de wrote:
On Sun, 2023-04-16 at 13:52 +0200, Iñaki Ucar wrote:
I agree that something like this would be a nice addition. With the
current condition system, it would be certainly easy (but quite a lot
of work) to define a hierarchy of built-in conditi
On Sun, 2023-04-16 at 13:52 +0200, Iñaki Ucar wrote:
> I agree that something like this would be a nice addition. With the
> current condition system, it would be certainly easy (but quite a lot
> of work) to define a hierarchy of built-in conditions, and then use
> them consistently throughout ba
As far as I know there are no reliable unique identifiers.
There appears to be a general drift towards classed conditions, but so
far only a small subset of conditions are generated that way (and to
tell you the truth, I forget how to detect one, even though I
contributed some of them to the p
On Sun, 16 Apr 2023 at 12:58, nos...@altfeld-im.de wrote:
>
> I am the author of the *tryCatchLog* package and want to
>
> - suppress selected conditions (warnings and messages)
> - rethrow selected conditions (e.g a specific warning as a message or to
> "rename" the condition text).
>
> I could
I am the author of the *tryCatchLog* package and want to
- suppress selected conditions (warnings and messages)
- rethrow selected conditions (e.g a specific warning as a message or to
"rename" the condition text).
I could not find any reliable unique identifier for each possible condition
- t
