Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interactive vs. non-interactive mode. #6

Open
joshuaguerin opened this issue Aug 2, 2021 · 2 comments
Open

Interactive vs. non-interactive mode. #6

joshuaguerin opened this issue Aug 2, 2021 · 2 comments

Comments

@joshuaguerin
Copy link
Owner

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).

@k-ericson
Copy link
Collaborator

perhaps done with an optional argument to the commands as written?
if that argument is present, just dump a skeleton?

@joshuaguerin
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants