nnako

Ah, ok. Thanks. Saw it. So we will add feature requests within the GitHub issues.

Hi, short question about the use of GitHub for discussions and issues. What about "feature requests"? Are they to be considered "issues" and put into GitHub in the future, or will they still be put into the SourceForge feature tracker? My suggestion would be to put feature requests into GitHub's issues as well and maybe tag / mark them in a special way to distinguish them from real bugs. What do you think?

don't remove comments in addressbook file

Hi @gibboris , thanks for your quick reply. I would think, that the effect of having to use the abook application with the --datafile argument, each time the application is called (from within mutt and from the command line) makes it necessary to always remember that location each time. But when the --datafile flag could be set within abook's configuration file (default is ~/.abook/abookrc) I could set it once there and forget about it in the future. As far as I have seen, there is no way to set...

don't override addressbook symlink

Interesting indeed. There could be one other point when trying to decide which user interface would be preferrable when choosing the behavior of "edit node core text". As we have seen, there are these options which would make sense: <F2> - usually (and still valid for the "old-style" themes) has the same effect as <END> but might be modified (and seems to have been modified for the L&F styles) to selecting the textual content of a node. ready to be overridden completely. <END> - go into edit mode...

Interesting indeed. There could be one other point when trying to decide which user interface would be preferrable when choosing the behavior of edit node content. As we have seen, there are these options which would make sense: <F2> - usually (and still valid for the "old-style" themes) has the same effect as <END> but might be modified (and seems to have been modified for the L&F styles) to selecting the textual content of a node. ready to be overridden completely. <END> - go into edit mode for...

Interesting indeed. There could be one other point when trying to decide which user interface would be preferrable when choosing the behavior of edit node content. As we have seen, there are these two options which would make sense: <F2> - usually (and still valid for the "old-style" themes) has the same effect as <END> but might be modified (and seems to have been modified for the L&F styles) to selecting the textual content of a node. ready to be overridden completely. <END> - go into edit mode...