Re: pwd and prompt don't update after deleting current working directory
On 2024-07-12 15:10, Chet Ramey wrote: On 7/11/24 9:53 PM, David Hedlund wrote: Thanks, Lawrence! I found this discussion helpful and believe it would be a valuable feature to add. Can I submit this as a feature request? I'm not going to add this. It's not generally useful for interactive shells, and dangerous for non-interactive shells. If this is a recurring problem for you, I suggest you write a shell function to implement the behavior you want and run it from PROMPT_COMMAND. That behavior could be as simple as pwd -P >/dev/null 2>&1 || cd .. Do you think that it would be appropriate to submit this feature request to the developers of the rm command instead. For comparision, caja (file manager in MATE) is stepping back as many directories as needed when it is located in a directory that is deleted in bash or caja.
Re: pwd and prompt don't update after deleting current working directory
On 7/16/24 3:47 AM, David Hedlund wrote: On 2024-07-12 15:10, Chet Ramey wrote: On 7/11/24 9:53 PM, David Hedlund wrote: Thanks, Lawrence! I found this discussion helpful and believe it would be a valuable feature to add. Can I submit this as a feature request? I'm not going to add this. It's not generally useful for interactive shells, and dangerous for non-interactive shells. If this is a recurring problem for you, I suggest you write a shell function to implement the behavior you want and run it from PROMPT_COMMAND. That behavior could be as simple as pwd -P >/dev/null 2>&1 || cd .. Do you think that it would be appropriate to submit this feature request to the developers of the rm command instead. You can try, but I would not expect them to implement it. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: pwd and prompt don't update after deleting current working directory
On Tue, Jul 16, 2024, at 3:47 AM, David Hedlund wrote: > Do you think that it would be appropriate to submit this feature request > to the developers of the rm command instead. How would this help? The rm utility cannot change the working directory of the shell that invokes it, or of any other process. Even if it could, that wouldn't help you if a different utility/application did the unlinking. (Never mind that there are no canonical "developers of the rm command". GNU is not the only implementation in the world.) > For comparision, caja (file manager in MATE) is stepping back as many > directories as needed when it is located in a directory that is deleted > in bash or caja. Behavior that is appropriate for GUI applications is not necessarily appropriate for CLI utilities, and vice versa. The comparison is inapt. -- vq
Re: pwd and prompt don't update after deleting current working directory
On 2024-07-16 15:31, Lawrence Velázquez wrote: On Tue, Jul 16, 2024, at 3:47 AM, David Hedlund wrote: Do you think that it would be appropriate to submit this feature request to the developers of the rm command instead. How would this help? The rm utility cannot change the working directory of the shell that invokes it, or of any other process. Even if it could, that wouldn't help you if a different utility/application did the unlinking. (Never mind that there are no canonical "developers of the rm command". GNU is not the only implementation in the world.) I appreciate your input. To be honest, I'm currently juggling multiple tasks and don't have the necessary bandwidth to fully consider this particular issue at the moment. Let's table this discussion for now. For comparision, caja (file manager in MATE) is stepping back as many directories as needed when it is located in a directory that is deleted in bash or caja. Behavior that is appropriate for GUI applications is not necessarily appropriate for CLI utilities, and vice versa. The comparison is inapt.
