labath added a comment. What exactly is the use case for this?
Having a place where the user can place lldb python scripts and have them be automatically accessible seems like a nice feature, but I am not convinced that $HOME is the right place for it. I definitely wouldn't want lldb scripts to litter my home directory, and if I started putting them in a subfolder, their import paths would get weird (particularly if they want to import one another). I think it'd be better if this was some subdirectory of $HOME. Since we already have $HOME/.lldb, maybe we could put this there (or some subdirectory thereof)? In D89295#2326782 <https://reviews.llvm.org/D89295#2326782>, @kastiglione wrote: > Could this have undesirable side effects? I wouldn't expect `command script > import` to be searching my home dir. Second question: is there value in > requiring the explicit use of `~`, for ex: `command script import ~/path`. That actually seems to work (if you add .py to the end). CHANGES SINCE LAST ACTION https://reviews.llvm.org/D89295/new/ https://reviews.llvm.org/D89295 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
