Stefan Monnier wrote:
> > I have not said it is more “standard for terminals”, I have that it
> > is more “standard” fullstop. It is more standard by the virtue of
> > having worked for decades, C-Ins S-Ins S-Del existed way before the
> > C-C C-V C-X tryptich, and still working today in most
On Wed, Feb 07, 2024 at 01:20:19PM +0100, Nicolas George wrote:
> Max Nikulin (12024-02-07):
> > It may be a convention for applications other than terminals, however I am
> > unsure what "standard" means for terminals.
>
> I have not said it is more “standard for terminals”, I have that it is
>
minals use
[Ctrl+Shift+c] and [Ctrl+Shift+v] instead of conventional [Ctrl+c] and
[Ctrl+v]. That is why I am against idea of adding [Ctrl+Insert] to xterm
bindings.
In Emacs C- is bound to `kill-ring-save'.
Works for me. The author of XTerm is quite reactive if you can explain
the issue cle
> I have not said it is more “standard for terminals”, I have that it is
> more “standard” fullstop. It is more standard by the virtue of having
> worked for decades, C-Ins S-Ins S-Del existed way before the C-C C-V C-X
> tryptich, and still working today in most contexts.
Indeed, IIUC these key
of having
worked for decades, C-Ins S-Ins S-Del existed way before the C-C C-V C-X
tryptich, and still working today in most contexts.
> Thanks, it seems, it works in bookworm. Several years ago xterm did not
> support ownership of independent CLIPBOARD and PRIMARY simultaneously.
--clipboard'", PRIMARY)\n\
copy-selection(CLIPBOARD)
… is simpler.
Thanks, it seems, it works in bookworm. Several years ago xterm did not
support ownership of independent CLIPBOARD and PRIMARY simultaneously.
It was a workaround for the following scenario:
- select so
On Sun 31 Dec 2023 at 00:43:40 (-0600), Mike McClain wrote:
> I
> suspect logging into a system where you have no home for your primary
> user might get interesting.
That problem is simple to resolve. I have encrypted /home partitions
on all my systems, but the root filesystem has a
be surprised if xterm-256color is just enough
different from xterm and lxterminal that that is why you don't see a
problem with the '"...": ...' syntax. If you have xterm-256color you
likely have xterm too. Have you tried it?
Thanks for showing me different ways of looking at my challenges.
Happ
On 30/12/2023 09:14, Mike McClain wrote:
Since some of these use a
spinoff of xterm [ -n $DISPLAY ] is a little more generic than
[ $TERM == xterm ], RaspberryPI has chosen lxterminal as their default
which would would fail that test but still runs bash.
I would expect that the reason
On Fri, Dec 29, 2023 at 08:14:37PM -0600, Mike McClain wrote:
> As it turns out every line in /mc/bin/xterm_bindings that
> was not a comment was problematic.From man readline or info readline
> I saw this: bind '"\C-x\C-r": re-read-init-file' and that is the syntax
> I used in xterm_bindings,
is McClain so /mc is where my
stuff goes to separate it from system stuff making it easier to move
my stuff from distribution to distribution. I started with DosLinux
back around 1997-8 and have used redhat, slakware, solaris, freebsd
and settled on Debian early this century. Since some of the
ental side effect.
>
> https://lists.debian.org/msgid-search/20110218064727.GA6305@playground
> Re: xterm question [SOLVED] Thu, 17 Feb 2011 22:47:27 -0800
That message is over 12 years old. It's quite likely some changes have
been made since then.
I'd also be curious to see w
I do not see anything that may cause the issue with single quote in the
following message. I am curious what was the goal of the particular
binding that had so detrimental side effect.
https://lists.debian.org/msgid-search/20110218064727.GA6305@playground
Re: xterm question [SOLVED] Thu, 17 Feb 2011 22:47:27 -0800
You guys were rigt all along, I just couldn't see it.
Greg's suggestion to try dash showed me the error of my ways.
I moved .inputrc to no.inputrc, commented out the line in
bash.environment that pulled in xterm_bindings, killed and restarted X
and sure enough I had '"' in an lxterminal window.
I
On 25/12/2023 12:31, Mike McClain wrote:
In lxterminal control v displays "'" though lxterminal doesn't.
Do xterm and lxterminal behave in a similar way? Is there something
related to xterm *VT100*translations in the output of
xrdb -query -
I am unsure if there are termina
On Mon, Dec 25, 2023 at 12:35:37PM -0600, Mike McClain wrote:
> root@RPI4b3:~> tty; echo $SHELL; echo "' " | hd
For the record, $SHELL does not tell you what shell you're currently in.
It tells you which login shell your account uses, or which shell
you'd *like* to use when you la
root@RPI4b3:~> tty; echo $SHELL; echo "' " | hd
/dev/tty1
/bin/bash
27 20 0a |' .|
0003
mike@RPI4b3:~> tty; echo $SHELL; echo "' " | hd
/dev/tty6
/bin/bash
27 20 0a |' .|
0003
On Sun, Dec 24, 2023 at 11:31:09PM -0600, Mike McClain wrote:
> I've examined /etc/inputrc, .inputrc, /etc/bash.bashrc, ~/.bashrc,
> /etc/profile, /etc/profile.d/*, ~/.profile, ~/.bash_profile,
OK, you've examined them... and... what did you *see* in them?
When did this problem start to happen,
This is reported by "xev" in response to the "'" key:
KeyPress event, serial 48, synthetic NO, window 0x1e1,
root 0x3af, subw 0x0, time 1860575, (170,-87), root:(1005,201),
state 0x10, keycode 48 (keysym 0x27, apostrophe), same_screen YES,
XLookupString gives 1 bytes: (27) "'"
On Sat, Dec 23, 2023 at 09:06:47PM -0500, Greg Wooledge wrote:
> On Sun, Dec 24, 2023 at 09:01:09AM +0700, Max Nikulin wrote:
> > On 24/12/2023 07:32, Mike McClain wrote:
> > > when I
> > > type a single quote "'" in bash xterm or lxterminal nothing shows.
>
On Sun, Dec 24, 2023 at 09:01:09AM +0700, Max Nikulin wrote:
> On 24/12/2023 07:32, Mike McClain wrote:
> > when I
> > type a single quote "'" in bash xterm or lxterminal nothing shows.
>
> May it happen that you have dead keys in your keyboard configuration to ty
On 24/12/2023 07:32, Mike McClain wrote:
when I
type a single quote "'" in bash xterm or lxterminal nothing shows.
May it happen that you have dead keys in your keyboard configuration to
type characters with accents? I have never used this feature, so my
guess may be wrong. Wh
On Sat, Dec 23, 2023 at 06:32:35PM -0600, Mike McClain wrote:
> I seldom use the command line while on the desk top since I keep 10
> VTs open for day to day tasks so only recently noticed that when I
> type a single quote "'" in bash xterm or lxterminal nothing shows.
I seldom use the command line while on the desk top since I keep 10
VTs open for day to day tasks so only recently noticed that when I
type a single quote "'" in bash xterm or lxterminal nothing shows. If
I open a file for editing with jed, my favorite editor, I can type a
si
On 10/15/23 04:44, to...@tuxteam.de wrote:
On Sun, Oct 15, 2023 at 03:34:52AM -0400, gene heskett wrote:
[...]
I can beat that Tomas. At one point in the early 90's we had a PDP-11 to run
a 7 meter C band dish, The VT 220 died and DEC wanted nearly 2G for a VT-550
This one keeps tripping me
On Sun, Oct 15, 2023 at 03:34:52AM -0400, gene heskett wrote:
[...]
> I can beat that Tomas. At one point in the early 90's we had a PDP-11 to run
> a 7 meter C band dish, The VT 220 died and DEC wanted nearly 2G for a VT-550
This one keeps tripping me up: the "G" in your "2G" means "grand",
On 10/15/23 02:06, to...@tuxteam.de wrote:
On Sun, Oct 15, 2023 at 09:52:16AM +0700, Max Nikulin wrote:
[...]
P.S. I believed that most confusing (while still useful) feature of
terminals is [Ctrl+s]. It takes some time to realize that it has been hit by
mistake, so [Ctrl+q] is required to
On Sun, Oct 15, 2023 at 09:52:16AM +0700, Max Nikulin wrote:
[...]
> P.S. I believed that most confusing (while still useful) feature of
> terminals is [Ctrl+s]. It takes some time to realize that it has been hit by
> mistake, so [Ctrl+q] is required to resume output.
Old age gotta have some
On 15/10/2023 02:10, Van Snyder wrote:
The culprit is tcsh, not XTerm. With bash, Alt-Shift-P produces a colon.
In tcsh the default bindings are almost the same as in bash:
https://manpages.debian.org/bookworm/tcsh/tcsh.1.en.html#history-search-backward
history-search-backward (M-p, M-P
The culprit is tcsh, not XTerm. With bash, Alt-Shift-P produces a
colon.
I added this to my .XDefaults
xterm*altIsNotMeta: truexterm*altSendsEscape: true
so that Alt-Shift-P becomes ESC-P. The problem now does not occur in
tcsh.
Thanks to the correspondents on the list.
On Sat, 2023-10-14 at 15:49
On Sat, Oct 14, 2023 at 08:38:22AM -0400, Greg Wooledge wrote:
> On Sat, Oct 14, 2023 at 07:07:57AM +0200, to...@tuxteam.de wrote:
> > On Fri, Oct 13, 2023 at 01:06:20PM -0700, Van Snyder wrote:
> > > I haven't figured out how to unlock the XTerm after accidentally giving
&g
On Sat, Oct 14, 2023 at 07:07:57AM +0200, to...@tuxteam.de wrote:
> On Fri, Oct 13, 2023 at 01:06:20PM -0700, Van Snyder wrote:
> > I haven't figured out how to unlock the XTerm after accidentally giving
> > it Alt-Shift-P.
I'm not seeing whatever it is you're seeing here. On
On Fri, Oct 13, 2023 at 01:06:20PM -0700, Van Snyder wrote:
> On Fri, 2023-10-13 at 12:38 -0700, Van Snyder wrote:
> > I have set up Alt-Shift-P as a macro in my editor (nedit) to run
> > pdflatex.
> > If I accidentally do it when XTerm has keyboard focus, it locks up
> &g
On Fri, 2023-10-13 at 12:38 -0700, Van Snyder wrote:
> I have set up Alt-Shift-P as a macro in my editor (nedit) to run
> pdflatex.
> If I accidentally do it when XTerm has keyboard focus, it locks up
> and the only thing I can do is kill it and restart.
> How can I unlock XT
I have set up Alt-Shift-P as a macro in my editor (nedit) to run
pdflatex.
If I accidentally do it when XTerm has keyboard focus, it locks up and
the only thing I can do is kill it and restart.
How can I unlock XTerm after doing this?
There are no Alt-Shift sequences listed at
https
On 21/08/2023 16:16, Karl Vogel wrote:
On Sun, Aug 20, 2023 at 10:38:34PM -0400, Max Nikulin wrote:
Xterm configuration options may be put to ~/.Xresources, e.g.
xterm*VT100.faceName: ...
I am curious if there are actual advantages of usage a wrapper script
instead of xresources
On Sun, Aug 20, 2023 at 10:38:34PM -0400, Max Nikulin wrote:
> On 20/08/2023 14:55, Karl Vogel wrote:
> > #!/bin/sh
> ...
> > # -fa 'xft:...' font size and weight
> ...
> > ( $XTERM $geo $topts -fa "$FONT" -title "Remote"
On 20/08/2023 14:55, Karl Vogel wrote:
#!/bin/sh
...
# -fa 'xft:...' font size and weight
...
( $XTERM $geo $topts -fa "$FONT" -title "Remote" ) &
Xterm configuration options may be put to ~/.Xresources, e.g.
xterm*VT100.faceName: ...
I am cur
Le mercredi 23 novembre 2022 à 08:50 +0100, Jean-Philippe Georget a écrit :
> Bonjour,
>
> Tout d'abord, je remercie tous les participants à ce fil de discussion qui
> m'ont permis de trouver une solution seulement aujourd'hui et après une bonne
> petite heure de recherche et de tests (car,
Bonjour,
Le 2022-11-23 08:50, Jean-Philippe Georget a écrit :
*Une explication*
Merci pour l'explication :)
Sébastien
Bonjour,
Tout d'abord, je remercie tous les participants à ce fil de discussion qui
m'ont permis de trouver une solution seulement aujourd'hui et après une bonne
petite heure de recherche et de tests (car, oui, je n'ai pas trouvé tout de
suite la solution ;-)
*Le problème*
Des caractères
Le 28/10/2022 10:30:41, Sébastien NOBILI a écrit :
> Pareil ici en lisant ton e-mail via Roundcube dans Firefox.
Pareil avec Balsa.
nicolas patrois : pts noir asocial
--
RÉALISME
M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ?
Un cerveau plus gros ?
P : Non...
Bonjour,
Le 2022-10-28 06:51, Jean-Philippe Georget a écrit :
Autre bizarrerie, un affichage du contenu du répertoire sous midnight
commander (mc) affiche les deux noms de fichiers correctement. J'ai
l'impression que les "é" sont affichés de la même manière à moins que
ls différences soient
Le Fri, 28 Oct 2022 07:55:47 +0200 (CEST),
Bernard Schoenacker a écrit :
> Bonjour,
>
> Pour des raisons de commodités, je vous conseille de
> passer par "detox" pour les noms de fichiers...
Oui et non. C'est très bien pour mettre sur un serveur web pas UTF8
dans les URL, mais je dois être
Bonjour,
Pour des raisons de commodités, je vous conseille de
passer par "detox" pour les noms de fichiers...
Documentation :
https://linux.die.net/man/1/detox
https://forum.ubuntu-fr.org/viewtopic.php?id=282633
Merci pour votre aimable attention
Bien à vous
Bernard
les deux noms de fichiers correctement. J'ai l'impression que les
"é" sont affichés de la même manière à moins que ls différences soient très
subtiles.
Le ven. 28 oct. 2022 11:10, Charles Plessy a écrit:
> From: Charles Plessy
> Subject: Re: Gestion de caractères accentués di
Le Fri, Oct 28, 2022 at 12:50:19AM +0200, Jean-Philippe Georget a écrit :
>
> Sous xterm, ce fichier s'affiche correctement comme "référent.pdf" avec la
> commande "ls".
>
> Par contre, sous xfce4-terminal, il s'affiche bizarrement comme
> "réfé
c ceux que je créée.
Sous xterm, ce fichier s'affiche correctement comme "référent.pdf" avec la
commande "ls".
Par contre, sous xfce4-terminal, il s'affiche bizarrement comme
"référent.pdf" (notez les accents décalés sur la droite des "e").
Quand j
On Mon, 12 Sep 2022, jindam, vani wrote:
i installed debian sid on userland app.
i have 2 terminals. xterm & uxterm. i have
installed openbox, jre, mc & palemoon.
i have 2 issues & both of are interrelated:
(1) when i start my vnc session, it
starts xterm terminal automatically
i installed debian sid on userland app.
i have 2 terminals. xterm & uxterm. i have
installed openbox, jre, mc & palemoon.
i have 2 issues & both of are interrelated:
(1) when i start my vnc session, it
starts xterm terminal automatically.
which file should i edit to start uxterm?
On Mon, Jun 13, 2022 at 05:57:00PM -0400, Michael Stone wrote:
> On Mon, Jun 13, 2022 at 05:53:59PM -0400, Michael Stone wrote:
> > When linux was first written, the IBM PC was 15 years old.
>
> *10
>
> I'm not sure if it's math or typing that's hard
All three of them, actually ;-)
Cheers
--
On Sun 12 Jun 2022 at 13:06:40 (-0600), Charles Curley wrote:
> On Sun, 12 Jun 2022 12:20:05 -0400
> gene heskett wrote:
>
> > Now, I really need a terminal for alt-ctl-F3 that does support the
> > mouse.
>
> charles@hawk:~$ apt show gpm
[ … ]
> Description: General Purpose Mouse interface
>
On Mon, Jun 13, 2022 at 05:53:59PM -0400, Michael Stone wrote:
When linux was first written, the IBM PC was 15 years old.
*10
I'm not sure if it's math or typing that's hard
On Mon, Jun 13, 2022 at 11:06:38AM -0400, gene heskett wrote:
On 6/13/22 09:17, Michael Stone wrote:
On Sun, Jun 12, 2022 at 08:19:02PM +0100, mick crane wrote:
The clue though is as somebody said that disabling this new
fangled EFI doesn't seem to do what Gene (or I ) thinks it does.
new
On Monday, June 13, 2022 11:35:29 AM Greg Wooledge wrote:
> Let's get some actual numbers in here. From wikipedia:
>
> IBM PC with proprietary BIOS introduced: 1981
> Linus Torvalds begins writing Linux: 1991
Efforts started toward EFI (predecessor in some sense of UEFI) -- see below:
On Mon, Jun 13, 2022 at 11:06:38AM -0400, gene heskett wrote:
> On 6/13/22 09:17, Michael Stone wrote:
> > new fangled? UEFI has been around longer than the PC BIOS was when linux
> > was first written...
> If that is what they taught you in history, Michael, sue the the school.
*sigh*
Let's
On 6/13/22 09:17, Michael Stone wrote:
On Sun, Jun 12, 2022 at 08:19:02PM +0100, mick crane wrote:
The clue though is as somebody said that disabling this new fangled
EFI doesn't seem to do what Gene (or I ) thinks it does.
new fangled? UEFI has been around longer than the PC BIOS was when
On Sun, Jun 12, 2022 at 08:19:02PM +0100, mick crane wrote:
The clue though is as somebody said that disabling this new fangled
EFI doesn't seem to do what Gene (or I ) thinks it does.
new fangled? UEFI has been around longer than the PC BIOS was when linux
was first written...
So having
On 2022-06-12 18:34, Roy J. Tellason, Sr. wrote:
On Sunday 12 June 2022 12:54:19 pm mick crane wrote:
As mentioned before, if it was me, I'd remove everything except the
disk
thing you want to boot with that has the OS on it and add and get
things
working one at a time afterwards.
Were I
On Sun, 12 Jun 2022 12:20:05 -0400
gene heskett wrote:
> Now, I really need a terminal for alt-ctl-F3 that does support the
> mouse.
charles@hawk:~$ apt show gpm
Package: gpm
Version: 1.20.7-8
Priority: optional
Section: misc
Maintainer: Axel Beckert
Installed-Size: 553 kB
Pre-Depends:
On Sun 12 Jun 2022 at 17:00:42 +, Andrew M.A. Cater wrote:
> On Sun, Jun 12, 2022 at 12:20:05PM -0400, gene heskett wrote:
> >
> > On 6/12/22 10:01, rhkra...@gmail.com wrote:
> > > On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
> > > > What I do
On Sunday 12 June 2022 12:54:19 pm mick crane wrote:
> As mentioned before, if it was me, I'd remove everything except the disk
> thing you want to boot with that has the OS on it and add and get things
> working one at a time afterwards.
Were I running into these kinds of hassles, that would
On Sun, Jun 12, 2022 at 12:20:05PM -0400, gene heskett wrote:
>
> On 6/12/22 10:01, rhkra...@gmail.com wrote:
> > On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
> > > What I do have is konsole and termit, no xterm.
> > For me, konsole does fine -- I c
On 6/12/22 12:41, Dan Ritter wrote:
gene heskett wrote:
On 6/12/22 10:01, rhkra...@gmail.com wrote:
On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
That's not the important first impression however. Installing without a root
pw, I am prevented from doing anything to the system
On Sun, Jun 12, 2022 at 11:42:06AM -0500, David Wright wrote:
> If blkid is missing, so is lsblk,
unicorn:~$ type blkid
blkid is /sbin/blkid
unicorn:~$ type lsblk
lsblk is /bin/lsblk
Betcha it's a PATH thing.
On 2022-06-12 17:20, gene heskett wrote:
I so want you to succeed and I can't be a lot of help.
As mentioned before, if it was me, I'd remove everything except the disk
thing you want to boot with that has the OS on it and add and get things
working one at a time afterwards.
mick
--
Key ID
On Sun 12 Jun 2022 at 12:20:05 (-0400), gene heskett wrote:
> On 6/12/22 10:01, rhkra...@gmail.com wrote:
> > On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
> > > What I do have is konsole and termit, no xterm.
> > For me, konsole does fine -- I can
gene heskett wrote:
>
> On 6/12/22 10:01, rhkra...@gmail.com wrote:
> > On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
> That's not the important first impression however. Installing without a root
> pw, I am prevented from doing anything to the system setup cuz everything
> but
On Sun 12 Jun 2022 at 03:53:49 (-0400), Felix Miata wrote:
> Thomas Schmitt composed on 2022-06-12 09:21 (UTC+0200):
> > Gene Heskett wrote:
>
> >> The fact remains that xterm is not in the pulldown menu's, I have konsole
> >> and termit, and termit will work from x
On 6/12/22 10:01, rhkra...@gmail.com wrote:
On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
What I do have is konsole and termit, no xterm.
For me, konsole does fine -- I can C from it with the mouse (and, presumably,
keystrokes).
Well, I gave up and did another 29t install
On Sunday, June 12, 2022 07:53:21 AM gene heskett wrote:
> What I do have is konsole and termit, no xterm.
For me, konsole does fine -- I can C from it with the mouse (and, presumably,
keystrokes).
I was going to restrain myself and not send this, but I succumbed ... sorry
for the noise.
On Sunday, June 12, 2022 03:53:49 AM Felix Miata wrote:
> Why this tangent to Gene's foibles?
I shouldn't do this, but ...
(And no criticism intended of anyone, specifically Thomas Schmitt.)
Hi,
it comes to me that Debian has an official screenshot of one of my xterms.
So here is an xterm with -bg wheat -fg black:
https://screenshots.debian.net/shrine/screenshot/15899/simage/large-de6e648f9ed3746646ab2120ba5da1f0.png
It is a bit higher than usual, to take all lines which i
Hi,
Gene Heskett wrote:
> xterm cannot be found by synaptic or apt either.
The package xterm exists and has versions in all current releases of Debian.
See:
https://tracker.debian.org/pkg/xterm
Try
sudo apt-get install xterm
or
sudo apt install xterm
> So I'll repeat
On Sun, Jun 12, 2022 at 08:08:49AM -0400, Greg Wooledge wrote:
> On Sun, Jun 12, 2022 at 07:53:21AM -0400, gene heskett wrote:
> > gene@coyote:~$ bash: xterm: command not found
> >
> > xterm cannot be found by synaptic or apt either.
>
> unicorn:~$ apt policy xterm
&g
On Sun, Jun 12, 2022 at 07:53:21AM -0400, gene heskett wrote:
> gene@coyote:~$ bash: xterm: command not found
>
> xterm cannot be found by synaptic or apt either.
unicorn:~$ apt policy xterm
xterm:
Installed: 366-1+deb11u1
Candidate: 366-1+deb11u1
Version table:
*** 366-1+de
On Sun, Jun 12, 2022 at 07:53:21AM -0400, gene heskett wrote:
> On Sunday, 12 June 2022 03:21:50 EDT Thomas Schmitt wrote:
> > Hi,
> >
> > Gene Heskett wrote:
> > > The fact remains that xterm is not in the pulldown menu's, I have
> > > konsole and termit,
On Sunday, 12 June 2022 03:21:50 EDT Thomas Schmitt wrote:
> Hi,
>
> Gene Heskett wrote:
> > The fact remains that xterm is not in the pulldown menu's, I have
> > konsole and termit, and termit will work from x and give me mouse
> > driven copy/ paste. But its a teeny l
Hi,
Felix Miata wrote:
> What purpose does an Xterm serve that can't be fulfilled by Konsole?
Dunno. xterm was proposed to Gene Heskett for use and he stated that
it's not available in the desktop menus.
> Why this tangent to Gene's foibles?
To give some tangible information and to
Thomas Schmitt composed on 2022-06-12 09:21 (UTC+0200):
> Gene Heskett wrote:
>> The fact remains that xterm is not in the pulldown menu's, I have konsole
>> and termit, and termit will work from x and give me mouse driven copy/
>> paste. But its a teeny litle thing on
Hi,
Gene Heskett wrote:
> The fact remains that xterm is not in the pulldown menu's, I have konsole
> and termit, and termit will work from x and give me mouse driven copy/
> paste. But its a teeny litle thing on this monitors screen.
Execute
xterm &
in one of the terminal
-18 07:12:36.0 +0300
+++ .config/bash/bashrc 2020-05-22 09:54:21.882114365 +0300
@@ -38,6 +38,9 @@
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
+rxvt*) color_prompt=yes;;
On Sun 05 Sep 2021 at 09:06:31 (-0400), Greg Wooledge wrote:
> On Sat, Sep 04, 2021 at 11:23:48PM -0500, David Wright wrote:
> > $ cat /var/local/lib/myhosts/colours/axis
> > 5 magenta bbarbutton=white,magenta,none:bbarhotkey=magenta,white,none
> > $
> >
> > 5 is for ANSI colours,
> > magenta
various terminals[2].
- Nate
[1] https://www.n0nb.us/blog/2020/02/tinkering-in-the-terminal-with-tput/
[2]
https://www.n0nb.us/blog/2020/02/coping-with-color-on-the-linux-console-and-xterm-and-friends/
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessi
On Sun, Sep 05, 2021 at 09:38:34AM -0400, Cindy Sue Causey wrote:
> There's also that thing about how terminals will interpret the
> different types of quotes (dumb/typewriter/ASCII versus
> typographic/curly/smart) very literally. I experienced THAT fail
> firsthand and now try to remember to
On 9/5/21, Greg Wooledge wrote:
> On Sun, Sep 05, 2021 at 12:28:37AM -0500, Intense Red wrote:
>> > In /root/.bashrc I use this to give a red prompt including host and
>> > full path followed by a new line.
>>
>>I take this idea a bit further, setting a longer prompt and setting
>>
On Sat, Sep 04, 2021 at 11:23:48PM -0500, David Wright wrote:
> $ cat /var/local/lib/myhosts/colours/axis
> 5 magenta bbarbutton=white,magenta,none:bbarhotkey=magenta,white,none
> $
>
> 5 is for ANSI colours,
> magenta is for, eg emacs, mutt, etc,
> bbarbutton is for mc.
>
> The lines from
On Sun, Sep 05, 2021 at 12:28:37AM -0500, Intense Red wrote:
> > In /root/.bashrc I use this to give a red prompt including host and
> > full path followed by a new line.
>
>I take this idea a bit further, setting a longer prompt and setting
> workstation hosts for specific colors for user
r brevity >
>
> # Then we need to export them so the shell picks things up.
> export PS1 LS_COLORS
>
>That's worth playing with to change some of the default settings if one
> wants to play with the colors of a terminal (I use KDE's "konsole" rather
> than
> xt
be on one long line.
# Then we need to export them so the shell picks things up.
export PS1 LS_COLORS
That's worth playing with to change some of the default settings if one
wants to play with the colors of a terminal (I use KDE's "konsole" rather than
xterm, but it's the same
On Fri 03 Sep 2021 at 02:45:03 (+0100), piorunz wrote:
> On 03/09/2021 01:34, David Wright wrote:
> > (I use my own customisations for distinct colours on each host,
> > and inverse colours for root's prompt.)
>
> Can you please share your root prompt invocation? Thanks!
Sure. The colours come
On 9/2/21 5:45 PM, piorunz wrote:
> On 03/09/2021 01:34, David Wright wrote:
>> (I use my own customisations for distinct colours on each host,
>> and inverse colours for root's prompt.)
>
> Can you please share your root prompt invocation? Thanks!
>
In /root/.bashrc I use this to give a red
On 03/09/2021 01:34, David Wright wrote:
(I use my own customisations for distinct colours on each host,
and inverse colours for root's prompt.)
Can you please share your root prompt invocation? Thanks!
--
With kindest regards, piorunz.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating
On Thu, Sep 2, 2021, 7:34 PM David Wright wrote
>
> (I use my own customisations for distinct colours on each host,
> and inverse colours for root's prompt.)
>
Good idea :-)
For some reason putting "root:" there doesn't save me 100% of the time :-)
Cheers,
> David.
>
>
On Fri 03 Sep 2021 at 03:15:13 (+0300), IL Ka wrote:
> .bashrc on bullseye contains following lines
>
> ```
> # set a fancy prompt (non-color, unless we know we "want" color)
> case "$TERM" in
> xterm-color|*-256color) color_prompt=yes;;
&g
Hi
.bashrc on bullseye contains following lines
```
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac
```
So we only have colors in the terminal emulator, but not in virtual
linux console.
Misschien dat een van jullie dat weet: sinds een paar weken is
copy/paste veranderd in een xterm. Eerst kon je een CR wel mee-pasten,
nu moet je een extra geven. Er is vast iets veranderd bij een
update, en het zal vast wel in een van de 7320 regels van de manpage
staan, maar om dat te gaan
On Monday, August 10, 2020 at 7:50:04 AM UTC-4, to...@tuxteam.de wrote:
> On Mon, Aug 10, 2020 at 12:14:30PM +0200, Marc SCHAEFER wrote:
> > On Sun, Aug 09, 2020 at 09:59:12AM +0200, tomas wrote:
> > > To verify/falsify that, you might run xprop on your xterm window.
>
On Mon, Aug 10, 2020 at 07:16:34PM +0200, Marc SCHAEFER wrote:
> On Mon, Aug 10, 2020 at 07:03:26PM +0200, Marc SCHAEFER wrote:
> > Should I try with another window-manager? I will also double-check that
> > the other working buster MATE installation uses marco.
>
> The bug is NOT present with
On Mon, Aug 10, 2020 at 07:03:26PM +0200, Marc SCHAEFER wrote:
> Should I try with another window-manager? I will also double-check that
> the other working buster MATE installation uses marco.
The bug is NOT present with compiz.
The bug IS NOT present on a fresh buster install with marco.
I
1 - 100 of 2538 matches
Mail list logo
