From 3d9217b5c021f5bd8e35b09eedfba8121aa051b1 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Wed, 28 Nov 2018 15:34:52 +0100 Subject: menuconfig: Clarify the scope of the named choice special-casing One thing that irks me a bit about it is that it might give the idea that menuconfigs have to include it, making things seem more complex than they really are. --- menuconfig.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/menuconfig.py b/menuconfig.py index 2d4c367..fd36abe 100755 --- a/menuconfig.py +++ b/menuconfig.py @@ -1421,6 +1421,9 @@ def _shown_nodes(menu): # # Note: Named choices are pretty broken in the C tools, and this is # super obscure, so you probably won't find much that relies on this. + # This whole 'if' could be deleted if you don't care about defining + # choices in multiple locations to add symbols (which will still work, + # just with things being displayed in a way that might be unexpected). # Do some additional work to avoid listing choice symbols twice if all # or part of the choice is copied in multiple locations (e.g. by -- cgit v1.2.3