From: imputerate <imputerate@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Xterm and Readline (was: select large text with mouse)
Date: Sun, 15 Jun 2008 00:49:34 -0700 (PDT) [thread overview]
Message-ID: <39241333-9551-477a-9a08-46a772611205@m73g2000hsh.googlegroups.com> (raw)
In-Reply-To: d42106c9-ac28-49a0-805c-37003756af4b@d45g2000hsc.googlegroups.com
On Jun 14, 1:24 pm, pturing <ptur...@gmail.com> wrote:
> > export INPUTRC=/etc/inputrc
> > export INPUTRC=/home/hodgson/.inputrc
> > --------------------------------------
>
> A couple things to note here:
>
> * Each of these export INPUTRC=foo lines is setting the INPUTRC
> variable, so the second one overwrites the value set by the first one.
> * You should not need either of these lines, since programs using
> readline will know to read in from the .inputrc file in your home
> directory by default
> * I think if you do have an .inputrc in your home directory, any
> entries in /etc/inputrc will not get read
from pturing's next post:
Your .profile already has a line that loads .bashrc. A period at the
beginning of a line is the same as source. So you have your .profile
calling .bashrc and your .bashrc calling .profile, which means its in
an infinite loop, so that's why you got a blank screen.
imputerate replies:
i can't find a line in .bashrc which calls .profile, but anyway...
taking in all four of pturing's points together:
i got rid of .profile, and /etc/inputrc;
then i commented out both 'export INPUTRC' lines in .bashrc;
when loaded Xterm/bash: the Readline customizations weren't active;
realizing that the line 'export INPUTRC=/etc/inputrc' WAS active in
the
.bashrc on the slackware box [where Readline IS active], i restored
that
line to my .bashrc on the ubuntu box: the customized keystrokes
delivered characters with
diacritical marks, like e with ` or ' on top [these are part of the
font
i 've set in .Xresources: "Emacs*font:
-*-lucida-medium-*-*-*-*-240-*-*-*-*-iso10646-* "
[a problem, anyway, because the spacing is proportional]
so, i commented out that line, and uncommented the export INPUTRC=/
home/hodgson/.inputrc line: this
time there were no weird characters, also no Readline stuff;
so, i restored the file, /etc/inputrc: same thing as before;
so, i restored the file ~/.profile [with no 'export INPUTRC' lines]:
same;
it looks like i have to tell somebody, somewhere to source some form
of
Readline configuration; i'll keep trying; any ideas? imputerate
next prev parent reply other threads:[~2008-06-15 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 1:26 select large text with mouse imputerate
2008-06-08 18:28 ` Joel J. Adamson
[not found] ` <mailman.12913.1212952149.18990.help-gnu-emacs@gnu.org>
2008-06-10 5:09 ` imputerate
2008-06-10 17:08 ` Joel J. Adamson
[not found] ` <mailman.13030.1213149142.18990.help-gnu-emacs@gnu.org>
2008-06-13 4:27 ` imputerate
2008-06-13 21:18 ` imputerate
2008-06-14 3:19 ` Xterm and Readline (was: select large text with mouse) Joel J. Adamson
[not found] ` <mailman.13226.1213413853.18990.help-gnu-emacs@gnu.org>
2008-06-14 5:01 ` imputerate
2008-06-14 5:39 ` imputerate
2008-06-14 18:24 ` pturing
2008-06-15 7:49 ` imputerate [this message]
2008-06-14 18:29 ` pturing
-- strict thread matches above, loose matches on Subject: below --
2008-06-14 5:43 imputerate
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39241333-9551-477a-9a08-46a772611205@m73g2000hsh.googlegroups.com \
--to=imputerate@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).