From d852bb27f2958948371ff20b6fbe40d2ced8ee50 Mon Sep 17 00:00:00 2001 From: Brian Leung Date: Tue, 3 Dec 2019 22:21:46 -0800 Subject: [PATCH] Silence byte-compiler warnings. --- virtualenvwrapper.el | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/virtualenvwrapper.el b/virtualenvwrapper.el index 5fafb90..c57b95c 100644 --- a/virtualenvwrapper.el +++ b/virtualenvwrapper.el @@ -24,6 +24,9 @@ ;; needed to set gud-pdb-command-name (require 'gud) +(require 'pcomplete) +(require 'subr-x) + ;; customizable variables (defgroup virtualenvwrapper nil @@ -43,7 +46,8 @@ you keep all your virtualenvs, or a list of strings, in which case it specifies disparate locations in which all your virtualenvs are kept. The default location is ~/.virtualenvs/, which is where your virtualenvs are stored if you use virtualenvwrapper in the shell." - :group 'virtualenvwrapper) + :group 'virtualenvwrapper + :type '(string)) (defcustom venv-dirlookup-names '(".venv" "venv") @@ -226,6 +230,9 @@ prompting the user with the string PROMPT" (defun venv-list-virtualenvs () (s-join "\n" (venv-get-candidates))) +(defvar python-shell-virtualenv-path) +(defvar eshell-path-env) + (defun venv--activate-dir (dir) "Given a directory corresponding to a virtualenv, activate it" (run-hooks 'venv-preactivate-hook) @@ -419,7 +426,7 @@ directories, the new virtualenvs are made in the current (venv-dir-to-name locs)))) venv-location))) (run-hooks 'venv-postrmvirtualenv-hook) - (when (called-interactively-p) + (when (called-interactively-p 'interactive) (message (concat "Deleted virtualenv: " it))))) ;;;###autoload @@ -551,6 +558,11 @@ virtualenvwrapper.el." (defmacro venv--make-pcompletions (commands) `(progn ,@(-map #'venv--gen-fun commands))) +(defvar eshell-modify-global-environment) + +(declare-function projectile-project-root "ext:projectile") +(declare-function eshell-stringify-list "esh-util") + ;;;###autoload (defun venv-initialize-eshell () "Configure eshell for use with virtualenvwrapper.el."