You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature and the current behavior/state
When a command redefinition via for example \renewcommand changes argument specification of the command, currently both the old (generated previously for \newcommand) and new completion entries are remembered. Ideally the old completion entries should be dropped.
This will not happen.
For this, txs would need to track the validity of each redefinition within a file as well as over where includes are placed.
The current architecture does not allow this and the effort seems too high for this corner case.
Describe the feature and the current behavior/state
When a command redefinition via for example
\renewcommand
changes argument specification of the command, currently both the old (generated previously for\newcommand
) and new completion entries are remembered. Ideally the old completion entries should be dropped.Who will benefit with this feature?
Users of LaTeX documents which alters argument specification(s) while redefining commands.
Any Other info
It occurred to me when reviewing #3924 and wondering "do
\renew...
commands needd1
modifier?"The text was updated successfully, but these errors were encountered: