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
The current version was written in a way where whatever information could be automatically parsed is generated automatically, and other info is typically pulled from the user by prompts in the minbuffer. I don't think we necessarily dislike this approach, but some users may want the ability to set interactive off deliberately in a .emacs file (i.e., just dump a documentation skeleton after parsing).
The text was updated successfully, but these errors were encountered:
Actually, I'm not certain that an argument is needed. My hypothesis is that this is likely an all or nothing scenario for most developers (i.e., I either want the goods or don't want it at all). If that is the case they could set a flag in their .emacs file to change the behavior from the default. Like (setq doqmnt_inter nil).
I'm thinking that tackling #3, #4, or #5, would result in similarly set configuration variables.
The current version was written in a way where whatever information could be automatically parsed is generated automatically, and other info is typically pulled from the user by prompts in the minbuffer. I don't think we necessarily dislike this approach, but some users may want the ability to set interactive off deliberately in a .emacs file (i.e., just dump a documentation skeleton after parsing).
The text was updated successfully, but these errors were encountered: