Shankar Rao <shankar....@gmail.com> writes: > Using ``org-speed-command-add'', I don't have to be concerned with > whether or not a given key is already present in > ``org-speed-commands''.
Sure. However, the same can be achieved with fairly simple Elisp, as you saw in the earlier messages. I do not clearly see how a significant number of users can really benefit from this command. Most people will simply not notice it. Beginners should better use customize interface. Power users can just write elisp. The only way I can see the proposed approach useful is creating a unified framework to set various non-trivial Org options programatically (like org-agenda-custom-commands). I would be in favour of merging such framework, but not individual commands. Having convenience setters for some customisations, but not other will be just confusing. Org already has a huge number of cusomisations. Alternatively, if many people jump in and say that your idea is very for them, the patch can be merged. > I agree that ``org-speed-command-add'' has undefined behavior when > provided with only a descriptive headline as its first element. Would > you be more amenable to this command if it either ignored or > explicitly disallowed descriptive headline entries? There is not much point discussing this part given the above issue I raised. Best, Ihor
