Hi list, It seems that `INCLUDE/` does not allow expanding `~/` or `$HOME` or other variables, and therefore can only support absolute paths with the user name hardcoded if files to include are located in a home subdirectory. I think this would be useful. Maybe an alternative would be to use `DO` with relative paths, but since `DO` depends on the locaation of the main reminders file, this may not cover all situations.
To illustrate my use case: I synchronize my reminders with git across multiple machines with different users, and therefore different absolute paths for their respective home directory. Remind automatically looks for a .rem file in `~/.reminders`, `~/.config/remind` or a path set in `DOTREMINDERS`, so a single reminders file and different user names are fine. However, if `INCLUDE` wants hardcoded paths, then user-specific files cannot be included without triggering warnings for non-existing paths, and things like `INCLUDE /usr/share/remind/holidays` cannnot be used either on immutable distributions whereby the Remind installation directory will contain a unique hash. Are there ways I may not know of to programmatically set `$HOME` or other variables inside the reminders file itself, using perhaps `SET` or by evaluating shell commands like `$(which remind)` to get its installation path? Apologies if I missed a way to do that in the manual. But even if that is possible, would it not make sense to support more parsimonious expansion of enironment variables and tilde in included paths automatically instead of expecting hardcoded paths only, like Remind does when looking for the reminders file? Thanks, and apologies if I missed something or am misusing Remind. Mat _______________________________________________ Remind-fans mailing list [email protected] https://dianne.skoll.ca/mailman/listinfo/remind-fans Remind is at https://dianne.skoll.ca/projects/remind/
