Comments (8)
@jsandovalc thanks for the report.
I guess we could pipe pipenv-run
commands into a pipenv-shell
buffer (including creating it if it does not yet exist). That would be a slightly more automated way to do what you are now doing as a workaround.
Some better solutions might be:
- To give a dedicated buffer to any command run by
pipenv-run
- To give info to the user via
*Pipenv*
about any runningpipenv-run
processes, and a way to manage these processes (i.e.: kill them).
Thoughts on what would work for your use case?
from pipenv.el.
I think both proposed solutions would work well for my workflow. But, I feel that pipenv run
would be better off creating a dedicated buffer for this kind of command. Maybe in this buffer I could do things like g
to restart (kill and run again) the command. I could eventually wrap it to create something similar to the elpy-django-runserver
function but for my particular use case.
Thanks again :) I feel this project has a lot of potential because emacs needs a good pipenv integration.
from pipenv.el.
@jsandovalc great, thanks for the feedback.
My general thinking was to iterate on *Pipenv*
towards a UI for pipenv.el
, instead of just a log of command outputs as it is now. That fits well with the idea of killing and restarting commands etc., and is I think more manageable then a buffer per pipenv-run
command, in the long run.
However, I'm not about to do that work anytime soon, so, I think the best solution for users as a next step will be to generate a new buffer for each pipenv-run
command, and have keybindings for start (if stopped), stop (kill), and restart.
I'm not sure when I will get to this, but I will certainly try to look at it in the coming weeks, and of course, I'd definitely be happy for a PR from you or anyone that implements something similar.
from pipenv.el.
I understand. The UI on Pipenv sounds really interesting. Would it be something similar to the magit UI?
My elisp knowledge is very shallow to implement changes for pipenv.el fast. I'm not even even sure how to setup an environment to develop an elisp extension. But it's something I've wanted to learn. I've only created some small functions in my setup for some simple things in my workflow. But I really want to integrate pipenv with emacs, so, this could be the motivation.
from pipenv.el.
The UI on Pipenv sounds really interesting. Would it be something similar to the magit UI?
Yes. Less complex, but yes.
My elisp knowledge is very shallow ...
So was mine before pipenv.el
;). Happy to help you with setup if you want to help out. Hacking on this and Emacs in general has been really fun for me! In any event, I'll update this issue before I start any work on this directly myself, so we (and others) can be in sync.
from pipenv.el.
Maybe it's a silly question, but I have doubts about how to develop an emacs extension I'm currently using. Should I disable it and import it from the github repo or maybe should I use a second clean instance of emacs for running the developing lib?.
Anyway, the first thing I'll try to do is run the tests.
Thanks!
from pipenv.el.
@jsandovalc not at all! It is one of those "easy, once you know how" things.
First, clone the pipenv.el
repo:
cd ~/Code
git clone https://github.com/pwalsh/pipenv.el.git
If you use use-package
, then adjust it to use :load-path
. For example:
(use-package pipenv
:demand t
:ensure nil
:load-path "~/Code/pipenv.el"
:hook python-mode)
If you don't use use-package
, then remove your normal way of loading pipenv.el
, and then add this to your init file:
(load "~/Code/pipenv.el")
Also, see the tasks you can run in the Makefile, and look at the CI configuration for their use.
from pipenv.el.
from pipenv.el.
Related Issues (20)
- Integration with live-py-mode not working HOT 5
- Documenting installing dev packages HOT 3
- pipenv.el bombs *Messages* and blocks minibuffer HOT 4
- Fix failing tests due to upstream change HOT 1
- Add prefix key customization
- C-c C-c not working... HOT 4
- Using pipenv from inside a subdirectory HOT 2
- Shell spawned by pipenv shell prints issued command before command output HOT 2
- Default key prefix conflicts with recent projectile HOT 2
- Feature: add ^U prefix to allow changing buffer name, like M-x shell does HOT 1
- (pipenv-executable-find "python") not working on Windows HOT 3
- Trailing color codes Issue HOT 2
- Looking for a new maintainer HOT 13
- Missing pyvenv dependency HOT 1
- After reopening the file within emacs session pipenv stops working HOT 4
- pipenv shell command fails on windows HOT 1
- pipenv--f-parent: Symbol’s function definition is void: f-expand HOT 1
- No such file or directory pipenv HOT 10
- No such file or directory, pipenv. And (executable-find "pipenv") returns nil HOT 1
- pipenv-activate freezes emacs on windows
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pipenv.el.