-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get textern to work with xvile, even with equivalent of gvim's "-f" option #19
Comments
Hmm, maybe? Are there any error messages from |
Yes, both ["gedit"] or ["gvim", "-f"] work OK. I can get xvile to run OK from a wrapper using xterm (as opposed to my default xfce4-terminal), I think that's probably because xterm is a separate 'proper' process whereas however many xfce4-terminal windows you have they are all the same process. Like gnome-terminal xfce4-terminal used tohave a 'start a separate process' option but no longer. I can probably get something acceptable going via an xterm. |
OK, I have something that works, and some things that don't work! ["rxvt","-e","vile"] - works in that I can edit the textarea with vile but I end up not being able to exit from rxvt/vile. I had to kill it with 'kill -9'. ["rxvt","-e","xvile"] - works OK, on exiting the editor (which is a GUI editor like gvim) the rxvt exits as well and there's no problems. ["rxvt","-iconic","-e","xvile"] - also works fine with the extra bonus of no rxvt window appearing ["myedit"] where myedit is a bash script - "rxvt -e vile $1" works perfectly, I'm not quite sure why it acts differently from doing things directly. Anyway I have a couple of reasonable workarounds now. |
I'm not familiar with |
I'm trying to get textern to work with my favourite editor xvile. This does have a "do not fork" option as follows:-
This blocks the parent process until xvile exits (I've tried it and it really does block). However when I set my editor in textern to ["xvile", "+fork"] it acts exactly the same as it does without the +fork. The xvile window opens but has no text in it and one can't type into it etc. Text input works back in the selected textarea.
Is it possible that textern isn't handling the rather strange +fork correctly as a command line option?
The text was updated successfully, but these errors were encountered: