Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
jsja == john s jacobs anderson [EMAIL PROTECTED] writes: Peter == Peter S Galbraith [EMAIL PROTECTED] writes: jsja Oh, no, I agree -- that's why I tend toward vi in those jsja situations. However, over the weekend I've been playing with jsja gnuserv/gnuclient in XEmacs, and I'm getting towards liking it. jsja Okay, that could work -- but I'm too forgetful to remember if there's jsja already an XEmacs process running -- anybody have a shell script that jsja will execute the following pseudocode? jsja if there's an XEmacs process running jsja `gnuclient -q $1` jsja else jsja `xemacs -nw $1` `fuser' is in the `psmisc' package. xg Description: Binary data
Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
Carel == Carel Fellinger [EMAIL PROTECTED] writes: Carel And to really speed up things, you could even use the -vanilla flag Carel next to -nw to tell xemacs to forget about all those nifty packages Carel that take all this time to load. Better to let it load it all up... have a sip of coffee and think about what edits you are going to make or something. Once it's running, using `gnuclient' is instant. `XG_INITIAL_XEMACS_ARGS=-unmapped xg' -- panel launcher button ;; `.emacs' (or .xemacs/init.el if you're set up that way) (when (member -unmapped command-line-args) (add-hook 'gnuserv-init-hook #'(lambda () (popup-dialog-box '(XEmacs is ready [Ok nil]) # .profile export EDITOR=xg xg Description: Binary data
Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
Chris == Chris Gray [EMAIL PROTECTED] writes: Chris People always get lots of responses from queries like this, Chris but this seems like the obvious way to do it: Chris pidof xemacs gnuclient -q $1 || xemacs -nw $1 Yep, that works. In the hopes of saving a newbie or two some time, here's _exactly_ what I put into ~/.bashrc: # for editing function gnue() { [ $# = 1 ] pidof xemacs gnuclient -q $1 || xemacs -nw $1; } After editing and saving the file, source it (. ~/.bashrc) at a shell prompt, and then gnue FILE will do the right thing. (Don't forget to put (gnuserv-start) in your .emacs file!) Thanks to Chris and the other people in the thread, john. -- [ John S Jacobs Anderson ]--URL:mailto:[EMAIL PROTECTED] [ Genehack: Not your daddy's weblog ]--URL:http://genehack.org
Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
On Mon, May 29, 2000 at 11:20:04PM -0400, Chris Gray wrote: pidof xemacs gnuclient -q $1 || xemacs -nw $1 This will only work if you are the one and only user ever to use xemacs. So you better use (analog to what was shown on the list a couple of days ago): $ fuser -sn tcp $((UID+21490)) gnuclient -q $1 || xemacs -nw $1 as gnuserver will open a user uniq tcp port on $((UID+21490)). And to really speed up things, you could even use the -vanilla flag next to -nw to tell xemacs to forget about all those nifty packages that take all this time to load. -- groetjes, carel
Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
Peter == Peter S Galbraith [EMAIL PROTECTED] writes: Peter Here's why I use gnuserv all the time. Say I in a shell in a Peter directory called Peter /deb/potato/home/rhogee/deb/gri/CVS/gri/doc/cookbook and I Peter want to edit a file in Emacs. I could go in Emacs and type Peter C-x C-f and then type in (or cut/paste) the whole path. Peter That's arduous. Oh, no, I agree -- that's why I tend toward vi in those situations. However, over the weekend I've been playing with gnuserv/gnuclient in XEmacs, and I'm getting towards liking it. Peter How to set it up (in slink anyway): [snip Peter's method] Okay, that could work -- but I'm too forgetful to remember if there's already an XEmacs process running -- anybody have a shell script that will execute the following pseudocode? if there's an XEmacs process running `gnuclient -q $1` else `xemacs -nw $1` Hmm -- I guess all I really need is the flag to test for a running process by name -- any help? thanks, john. -- [ John S Jacobs Anderson ]--URL:mailto:[EMAIL PROTECTED] [ Genehack: Not your daddy's weblog ]--URL:http://genehack.org
Re: Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
On Mon, May 29, 2000 at 10:58:08PM -0400, john s jacobs anderson wrote: Okay, that could work -- but I'm too forgetful to remember if there's already an XEmacs process running -- anybody have a shell script that will execute the following pseudocode? if there's an XEmacs process running `gnuclient -q $1` else `xemacs -nw $1` Hmm -- I guess all I really need is the flag to test for a running process by name -- any help? People always get lots of responses from queries like this, but this seems like the obvious way to do it: pidof xemacs gnuclient -q $1 || xemacs -nw $1 Cheers, Chris -- pick, pack, pock, puck: like drops of water in a fountain falling softly in the brimming bowl.
Using gnuserv (Re: bigots - was Emacs - was Mail/news software)
Here's why I use gnuserv all the time. Say I in a shell in a directory called /deb/potato/home/rhogee/deb/gri/CVS/gri/doc/cookbook and I want to edit a file in Emacs. I could go in Emacs and type C-x C-f and then type in (or cut/paste) the whole path. That's arduous. Instead, if I want to edit a file called Makefile, from the shell I type $ e Makefile and it magically pops up in Emacs. How to set it up (in slink anyway): Step 1) install the gnuserv package Step 2) insert the following in your ~/emacs file : (gnuserv-start) Step 3) Optionally, create a short-cut alias name for `gnuclient -q` by inserting the following in your shell startup file, ~/.tcshrc for me alias e gnuclient -q Step 4) start Emacs Step 5) type from the shell: $ e somefile or $ gnuclient -q somefile Step 6) Oh wait... There's no step 6! :-) Peter john s jacobs anderson wrote: Peter == Peter S Galbraith [EMAIL PROTECTED] writes: Peter Felix Natter wrote: john s jacobs anderson [EMAIL PROTECTED] writes: Oh, I'm with you -- I'll often use vi for small edits, even if I have XEmacs open on another desktop, just because doing the edit 'in-line' in an xterm fits my work-flow better. Again, it's all about choosing the right tool for the job. you can do emacs -nw (no windowing). Peter Or use gnuserv. Gnuserv is on that eternally-growing list of things that I need to check out, learn, and integrate into my toolkit. Alas, I'm not there yet, so I keep reaching for the vi out of habit.