[Rpm-maint] [rpm-software-management/rpm] Implement support for literal and one-shot macro modifiers (PR #4129)

[Vít Ondruch]

voxik left a comment (rpm-software-management/rpm#4129)

> I don't see what purpose a "default" modifier would achieve: if you don't want modifiers, you just leave it out. Explicitly denying empty `<>` seems like more trouble for no benefit at all, but I could be convinced otherwise with an actual case to show why it's bad.

Basically, what I am not clear is how many behaviors there are. Are there three? Or maybe just two, where in fact `o` or `l` would be default?

Maybe simple documentation change from `Macro behavior can be altered by supplying modifiers` to `The default macro behavior can be altered by supplying (additional) modifiers` would make it more obvious.

BTW, proposing this change, maybe it could also make sense to say singular `modifier` to be clear that only one can be applied at time.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4129#issuecomment-3996730557
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4129/c3996730557 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260304/9ed401a3/attachment-0001.htm>