all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pepijn Kenter <kenter_remove_spam@tpd.tno.nl>
Subject: Re: GNU emacs locks files modified with CVS
Date: Wed, 17 Dec 2003 17:41:56 +0100	[thread overview]
Message-ID: <3FE08754.1050209@tpd.tno.nl> (raw)
In-Reply-To: mailman.195.1071679031.868.help-gnu-emacs@gnu.org

gebser@speakeasy.net wrote:
> Of course everyone can set up their systems however they wish, but I 
> use:

Of course. When saying the .bashrc isn't the proper place for setting 
the DISPLAY variable, I meant that at that time you can't know what 
value to set it to. From your (and Maurizio Loreti's) post I learned you 
can use the who command to find out. So thank you both.

> 
> export DISPLAY=$(who -lum|awk -F '(' '{print $2}'|awk -F ')' '{print $1}'):0
> 
> in my ~/.bashrc and have no problem logging in and/or running remotely
> whatever X apps I want.
> 
> Because it would take a lot of thinking to hash out which is the correct 
> file to put this in, whether the DISPLAY is a resource or not, whether...<snip>

Excuse my ignorance, but what do you mean by resource in this context?

Pepijn.

  parent reply	other threads:[~2003-12-17 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.195.1071679031.868.help-gnu-emacs@gnu.org>
2003-12-17 16:26 ` GNU emacs locks files modified with CVS Kevin Rodgers
2003-12-17 19:03   ` gebser
2003-12-17 16:41 ` Pepijn Kenter [this message]
2003-12-17 17:54 ` Maurizio Loreti
2003-12-18 17:19   ` Kevin Rodgers
     [not found] <mailman.138.1071587578.868.help-gnu-emacs@gnu.org>
2003-12-16 14:51 ` Pepijn Kenter
2003-12-16 16:26   ` gebser
2003-12-17  6:42   ` Maurizio Loreti
2003-12-17 15:34     ` gebser
2003-12-15 12:25 Pepijn Kenter
2003-12-15 18:04 ` Kevin Rodgers
2003-12-16  9:44   ` Pepijn Kenter
2003-12-16 14:10     ` gebser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FE08754.1050209@tpd.tno.nl \
    --to=kenter_remove_spam@tpd.tno.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.