| commit | a712cec60fbb9a3384f209f96d43b8e3dfd2d9ce | |
| author | Karl Fogel <kfogel@red-bean.com> | |
| Mon, 24 Nov 2014 17:32:42 +0000 (24 11:32 -0600) | ||
| committer | Nicolas Goaziou <mail@nicolasgoaziou.fr> | |
| Tue, 25 Nov 2014 08:23:36 +0000 (25 09:23 +0100) | ||
| tree | cf77c7f497618e9e744a983c4a57170a6161f6d8 | treesnapshot (tar.gz zip) |
| parent | aa65ac35aa4c82cf4db9d5bc6bff55afb3a9089b | commitdiff |
org.el: Improve accuracy of message
* lisp/org.el (org-remove-file): Reword success message.
Before this change, when `org-remove-file' succeeded in removing a
file from `org-agenda-files', it would display this unduly alarming
message to the user: "Removed file: foo.org". This made it seem as
though the file itself were removed from the filesystem, rather than
simply being delisted from `org-agenda-files'.
After this change, the message "Removed from Org Agenda list: foo.org"
is displayed instead, so the user will experience only the normal
level of panic involved in using Org Mode, not the increased panic
that results from thinking a file has been removed when it hasn't.
TINYCHANGE
* lisp/org.el (org-remove-file): Reword success message.
Before this change, when `org-remove-file' succeeded in removing a
file from `org-agenda-files', it would display this unduly alarming
message to the user: "Removed file: foo.org". This made it seem as
though the file itself were removed from the filesystem, rather than
simply being delisted from `org-agenda-files'.
After this change, the message "Removed from Org Agenda list: foo.org"
is displayed instead, so the user will experience only the normal
level of panic involved in using Org Mode, not the increased panic
that results from thinking a file has been removed when it hasn't.
TINYCHANGE
| lisp/org.el | diffblobblamehistory |