Re: [O] Documentation suggestion re: buffers containing crypted entries
I think we can disable auto-save locally using file variables, but what org-crypt seem to check is auto-save-default and its value probably won't change when auto-save is disabled locally. -- Darlan Cavalcante At Mon, 27 Jun 2011 18:56:54 +0200, Bastien b...@altern.org wrote: Hi Eric, Eric S Fraga e.fr...@ucl.ac.uk writes: The question is where should this information be most appropriate to appear. In my view, this should be in the documentation (highlighted etc), not in the Emacs mini-buffer! I don't know enough texi (any at all, actually) so cannot suggest a patch. However, I would suggest that the warning that is in the code be moved into the entry for org-crypt.el in the info manual. I did so -- I added this to the config example in org.texi: , | (setq auto-save-default nil) | ;; Auto-saving does not cooperate with org-crypt.el: so you need | ;; to turn it off if you plan to use org-crypt.el quite often. | ;; Otherwise, you'll get an (annoying) message each time you | ;; start Org. | | ;; To turn it off only locally, you can insert this: | ;; | ;; # -*- buffer-auto-save-file-name: nil; -*- ` Or, as originally proposed, the warning in the code could be wrapped in a customisable variable but this seems like overkill to me. To me too, unless we have a clean way to disable auto-save-mode locally. Just my 2¢! 2thx! -- Bastien
Re: [O] Documentation suggestion re: buffers containing crypted entries
Hi Bill, Bill Day williamson@gmail.com writes: # -*- buffer-auto-save-file-name: nil; -*- Do you know if this hack works for recent Emacsen without side-effects? -- Bastien
Re: [O] Documentation suggestion re: buffers containing crypted entries
Hi Eric, Eric S Fraga e.fr...@ucl.ac.uk writes: The question is where should this information be most appropriate to appear. In my view, this should be in the documentation (highlighted etc), not in the Emacs mini-buffer! I don't know enough texi (any at all, actually) so cannot suggest a patch. However, I would suggest that the warning that is in the code be moved into the entry for org-crypt.el in the info manual. I did so -- I added this to the config example in org.texi: , | (setq auto-save-default nil) | ;; Auto-saving does not cooperate with org-crypt.el: so you need | ;; to turn it off if you plan to use org-crypt.el quite often. | ;; Otherwise, you'll get an (annoying) message each time you | ;; start Org. | | ;; To turn it off only locally, you can insert this: | ;; | ;; # -*- buffer-auto-save-file-name: nil; -*- ` Or, as originally proposed, the warning in the code could be wrapped in a customisable variable but this seems like overkill to me. To me too, unless we have a clean way to disable auto-save-mode locally. Just my 2¢! 2thx! -- Bastien
Re: [O] Documentation suggestion re: buffers containing crypted entries
Dave Abrahams d...@boostpro.com writes: I was hit by this last week when I was investigating why my emacs initialization was taking so long. Later I found out that org-crypt was the culprit, since it added a sit for 5s in order for the user to actually see this warning. The problem is that org-crypt tests the value of the auto-save-default variable during loading time. This reflects the default behavior and not the actual auto-save status of the current buffer. Maybe a variable to disable this warning could be introduced so that the user could disable it after understanding the problem. Oh, yes please! I'm finding the delays introduced by this problem almost intolerable. Call me picky but I've gone to great lengths to make emacs very responsive and this sit-for really interferes! +1 I have found this (sit-for 5) annoying enough that I have deleted it from my copy of org. 5 seconds is a large percentage of my emacs start up time! thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.430.g95fa2.dirty)
Re: [O] Documentation suggestion re: buffers containing crypted entries
Eric S Fraga e.fr...@ucl.ac.uk writes: Dave Abrahams d...@boostpro.com writes: I was hit by this last week when I was investigating why my emacs initialization was taking so long. Later I found out that org-crypt was the culprit, since it added a sit for 5s in order for the user to actually see this warning. The problem is that org-crypt tests the value of the auto-save-default variable during loading time. This reflects the default behavior and not the actual auto-save status of the current buffer. Maybe a variable to disable this warning could be introduced so that the user could disable it after understanding the problem. Oh, yes please! I'm finding the delays introduced by this problem almost intolerable. Call me picky but I've gone to great lengths to make emacs very responsive and this sit-for really interferes! +1 I have found this (sit-for 5) annoying enough that I have deleted it from my copy of org. 5 seconds is a large percentage of my emacs start up time! I also have removed this wait in my local copy of org-mode. I use org-crypt for one subtree in each of my org files which contains passwords and other sensitive data. I rarely decrypt these entries so leaving auto save on for my use case isn't much of a security issue for me. I tend to decrypt the entry, look up the detail I need, and then resave the file which reencrypts the entry immediately. Just my 2 cents :) -- Bernt
Re: [O] Documentation suggestion re: buffers containing crypted entries
Eric S Fraga e.fr...@ucl.ac.uk writes: I have found this (sit-for 5) annoying enough that I have deleted it from my copy of org. 5 seconds is a large percentage of my emacs start up time! I just reduced it to one second. Still, the message needs some time to appear to the user. -- Bastien
Re: [O] Documentation suggestion re: buffers containing crypted entries
Bastien b...@altern.org writes: Eric S Fraga e.fr...@ucl.ac.uk writes: I have found this (sit-for 5) annoying enough that I have deleted it from my copy of org. 5 seconds is a large percentage of my emacs start up time! I just reduced it to one second. Still, the message needs some time to appear to the user. The question is where should this information be most appropriate to appear. In my view, this should be in the documentation (highlighted etc), not in the Emacs mini-buffer! I don't know enough texi (any at all, actually) so cannot suggest a patch. However, I would suggest that the warning that is in the code be moved into the entry for org-crypt.el in the info manual. Or, as originally proposed, the warning in the code could be wrapped in a customisable variable but this seems like overkill to me. One quickly becomes inured to messages that appear every time you use a tool. At best, they are simply ignored; at worst, they become annoying, such as in this case. I'm not complaining critically as it is trivial to fix for my own use. Just my 2¢! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.430.g95fa2.dirty)
Re: [O] Documentation suggestion re: buffers containing crypted entries
I was hit by this last week when I was investigating why my emacs initialization was taking so long. Later I found out that org-crypt was the culprit, since it added a sit for 5s in order for the user to actually see this warning. The problem is that org-crypt tests the value of the auto-save-default variable during loading time. This reflects the default behavior and not the actual auto-save status of the current buffer. Maybe a variable to disable this warning could be introduced so that the user could disable it after understanding the problem. Oh, yes please! I'm finding the delays introduced by this problem almost intolerable. Call me picky but I've gone to great lengths to make emacs very responsive and this sit-for really interferes! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] Documentation suggestion re: buffers containing crypted entries
I was hit by this last week when I was investigating why my emacs initialization was taking so long. Later I found out that org-crypt was the culprit, since it added a sit for 5s in order for the user to actually see this warning. The problem is that org-crypt tests the value of the auto-save-default variable during loading time. This reflects the default behavior and not the actual auto-save status of the current buffer. Maybe a variable to disable this warning could be introduced so that the user could disable it after understanding the problem. -- Darlan At Sat, 30 Apr 2011 17:34:06 -0400, Bill Day williamson@gmail.com wrote: [1 text/plain; ISO-8859-1 (7bit)] I appreciate the warning about encrypted entries, and, I would like to add, all the hard work and careful thought that has gone into making org-mode such an incredible piece of software. I checked the documentation regarding turning off auto-save on pages containing encrypted entries and saw that the warning was repeated but there was no advice on how to implement it. See http://orgmode.org/worg/org-tutorials/encrypting-files.html My eventual solution (there may be better ones) was to add a line at the top of my encrypted page as follows: # -*- buffer-auto-save-file-name: nil; -*- This itself generates a warning every time I go to that page, but it seems to inhibit auto-save. I would like to suggest that a little bit of explanation of how to turn auto-save on and off be added to the documentation on encryption with org-mode. Thank you. Sincerely, Bill Day -- Bill Day williamson@gmail.com [2 text/html; ISO-8859-1 (quoted-printable)]
[O] Documentation suggestion re: buffers containing crypted entries
I appreciate the warning about encrypted entries, and, I would like to add, all the hard work and careful thought that has gone into making org-mode such an incredible piece of software. I checked the documentation regarding turning off auto-save on pages containing encrypted entries and saw that the warning was repeated but there was no advice on how to implement it. See http://orgmode.org/worg/org-tutorials/encrypting-files.html My eventual solution (there may be better ones) was to add a line at the top of my encrypted page as follows: # -*- buffer-auto-save-file-name: nil; -*- This itself generates a warning every time I go to that page, but it seems to inhibit auto-save. I would like to suggest that a little bit of explanation of how to turn auto-save on and off be added to the documentation on encryption with org-mode. Thank you. Sincerely, Bill Day -- Bill Day williamson@gmail.com
