Re: Bash command completion

> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote: > > So have you followed the suggestion to test whether it is in fact bash that > you are in fact using? Yes. And I wasn't -- it was dash. So I: 'chsh -s /bin/bash' 'ls Do\t' and got a tab. > lisi@Tux-

Re: Bash command completion

c/bash.bashrc to enable completion. The commands are: > > > > # enable bash completion in interactive shells > > #if ! shopt -oq posix; then > > # if [ -f /usr/share/bash-completion/bash_completion ]; then > > #. /usr/share/bash-completion/bash_completion > >

Re: Bash command completion

> On Jul 6, 2016, at 3:16 PM, Sven Arvidsson wrote: > > Are you sure that your user uses bash for the login shell? There was a > transition from bash to dash some releases ago. Nope. According to 'man sh', it's dash. I understood that dash is a fixed bash. But why

Re: Bash command completion

> On Jul 6, 2016, at 2:29 PM, Charlie Kravetz > wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > There should be a set of commands towards the bottom > of /etc/bash.bashrc to enable completion. The commands are: > > # enable bash completion in in

Re: Bash command completion

On Wed, 2016-07-06 at 14:29 -0600, Charlie Kravetz wrote: > On Wed, 6 Jul 2016 13:48:24 -0600 > Glenn English wrote: > > > > > I put wheezy on a 386 computer last night ('aptitude dist-upgrade' > > from squeeze -- it'd been in the junk box for a while

Re: Bash command completion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 6 Jul 2016 13:48:24 -0600 Glenn English wrote: >I put wheezy on a 386 computer last night ('aptitude dist-upgrade' from >squeeze -- it'd been in the junk box for a while), and when I hit tab, bash >just gives me

Bash command completion

I put wheezy on a 386 computer last night ('aptitude dist-upgrade' from squeeze -- it'd been in the junk box for a while), and when I hit tab, bash just gives me a tab -- I have to type the whole command manually. This happens only for the user; root works fine. I've copied

Re: nother bash question

on on a reply > from inotifywait.) > inotifywait does that, only returning with the name when the file has been closed. Now, I've been doing a little cleanup, so here is the current version to pick apart. It IS working with no errors. = #!/bin/bash # set -x # this was a test, wa

Re: nother bash question

The syntax problem is most probably about missing "-quotes around > > the variable ecaluation ${InMail} which would have to be empty to > > cause the message: > > > > $ test $notdefined = "hello world" > > -bash: test: =: unary operator expected > &g

Re: nother bash question

On Monday 13 June 2016 08:50:58 Jörg-Volker Peetz wrote: > watch -d -n 1.5  ls -la /var/spool/mail/ Interesting tool, thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Ge

Re: nother bash question

Hi, > ++ /usr/bin/inotifywait -q -e close --format %f /var/spool/mail/ >From the man page i learn that you let it watch the whole directory. This way you get notifications about any file in there. The empty variable content possibly stems from this feature: "-format ... %f When an ev

Re: nother bash question

On Monday 13 June 2016 06:34:00 Gene Heskett wrote: > On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > > Hi, > > > > > > Gene Heskett wrote: > > > > if test ${InMail} = "gene" > > > > bin/mailwatcher: line 66: test: =:

Re: nother bash question

first name basis with both fetchmail and procmail too. This completely offloads the mail fetching by your email agent, in this case kmail, so its getmail functions are automatic, on demand and fractional seconds to do, paced by the -d time argument in your ~/.fetchmailrc: =

Re: nother bash question

Hi, David Wright wrote: > Thomas, your patience appears unbounded. That's a character strength which a programmer must have at least in part. > https://lists.debian.org/debian-user/2016/04/msg00652.html Yeah. I advised Gene to put "-quotes around variable evaluations. Now we have the education

Re: nother bash question

On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > Hi, > > > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probabl

Re: nother bash question

expected > > > > The syntax problem is most probably about missing "-quotes around > > the variable ecaluation ${InMail} which would have to be empty to > > cause the message: > > > > $ test $notdefined = "hello world" > > -bash: test: =: u

Re: nother bash question

riable ecaluation ${InMail} which would have to be empty to > cause the message: > > $ test $notdefined = "hello world" > -bash: test: =: unary operator expected > $ test "$notdefined" = "hello world" > > $ defined=x > $ test $de

Re: nother bash question

Gene Heskett wrote on 06/13/16 12:34: > In any event a pair of "" around the left argument silenced the warning, > and it still works. However it may be that inotifywait is premature, as > I see that InMail occasionall contains a hash name of the order of: > + test _KQG,TdoXXB.coyote = gene > +

Re: nother bash question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 13, 2016 at 12:30:39PM +0200, Thomas Schmitt wrote: > Hi, [...] > to...@tuxteam.de wrote: > > One could argue "unary operator expected" is a strange way to > > restate this. > > It's the way how the gild of land surveyors and bean counte

Re: nother bash question

On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > Hi, > > > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probabl

Re: nother bash question

Hi, i wrote: > > Is ${InMail} supposed to be empty ? Gene Heskett wrote: > That is set by inotifywait's return of the name of the file that procmail > just closed. Hmm. I don't have inotifywait installed. According to http://linux.die.net/man/1/inotifywait it should put out lines like CLOSE_

Re: nother bash question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > Hi, > > Gene Heskett wrote: > > if test ${InMail} = "gene" > > bin/mailwatcher: line 66: test: =: unary operator expected > > The syntax problem is most probably about missing "-quotes

Re: nother bash question

the variable ecaluation ${InMail} which would have to be empty to > cause the message: > > $ test $notdefined = "hello world" > -bash: test: =: unary operator expected > $ test "$notdefined" = "hello world" > > $ defined=x > $ test $def

Re: nother bash question

$notdefined = "hello world" -bash: test: =: unary operator expected $ test "$notdefined" = "hello world" $ defined=x $ test $defined = "hello world" $ Another negative syntax effect would happen if ${InMail} did consist of more than one word:

nother bash question

Greetings bashers; I have a set -x at the top of this script, and this line, while working as expected: if test ${InMail} = "gene" also spits out this warning: bin/mailwatcher: line 66: test: =: unary operator expected What syntax correction does this need? Thanks. Cheers, Gene Heskett -- "

Re: bash help please

), and so on up to the top-level (user interface). 3. Automate as much as possible -- building, testing, installing, packaging, releasing, etc.. David p.s. A digression -- while Bourne/ Bash shell have some very intriguing capabilities and both exist almost universally in FOSS realm

Re: bash help please

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 09, 2016 at 10:41:27PM -0400, Gene Heskett wrote: > Greetings; > > A bash script that has worked most of a decade now refuses. > > For instance, assume that var InMail is = "gene", and can be echoed from

Re: bash help please

On Friday 10 June 2016 01:34:14 David Wright wrote: > On Fri 10 Jun 2016 at 01:04:40 (-0400), Gene Heskett wrote: > > On Thursday 09 June 2016 23:50:35 David Wright wrote: > > > On Thu 09 Jun 2016 at 22:41:27 (-0400), Gene Heskett wrote: > > > > A bash script that h

Re: bash help please

On Fri 10 Jun 2016 at 01:04:40 (-0400), Gene Heskett wrote: > On Thursday 09 June 2016 23:50:35 David Wright wrote: > > On Thu 09 Jun 2016 at 22:41:27 (-0400), Gene Heskett wrote: > > > A bash script that has worked most of a decade now refuses. > > > > > > For

Re: bash help please

On Friday 10 June 2016 00:00:12 David Christensen wrote: > On 06/09/2016 07:41 PM, Gene Heskett wrote: > > A bash script that has worked most of a decade now refuses. > > > > For instance, assume that var InMail is = "gene", and can be echoed > > from the

Re: bash help please

On Thursday 09 June 2016 23:50:35 David Wright wrote: > On Thu 09 Jun 2016 at 22:41:27 (-0400), Gene Heskett wrote: > > A bash script that has worked most of a decade now refuses. > > > > For instance, assume that var InMail is = "gene", and can be echoed > >

Re: bash help please

gt; Lars I am about to call up a copy of amrecover, and restore that script to one that was working last week, I cannot get by the syntax errors between fi & done in a while loop with a bunch of if-then-elif-fi's in it. Last weeks wasn't perfect, but it did work, and everytime I l

Re: bash help please

On 06/09/2016 07:41 PM, Gene Heskett wrote: A bash script that has worked most of a decade now refuses. For instance, assume that var InMail is = "gene", and can be echoed from the command line using $InMail like this. gene@coyote:~$ echo $InMail gene But I'll be switched if I c

Re: bash help please

On Thu 09 Jun 2016 at 22:41:27 (-0400), Gene Heskett wrote: > A bash script that has worked most of a decade now refuses. > > For instance, assume that var InMail is = "gene", and can be echoed from > the command line using $InMail like this. > gene@coyote:~$ echo $In

Re: bash help please

On 06/10/2016 05:41 AM, Gene Heskett wrote: > gene@coyote:~$ echo `test [${InMail} = "gene"]` > > All I get is the linefeed. Obviously I'm losing it, so how do I > translate and get usefull output for troubleshooting? One option is to use 'set -x' there in the script. It can go anywhere above

bash help please

Greetings; A bash script that has worked most of a decade now refuses. For instance, assume that var InMail is = "gene", and can be echoed from the command line using $InMail like this. gene@coyote:~$ echo $InMail gene But I'll be switched if I can get a result from a line of

Re: bash - shell events "!"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 11:32:47AM +0200, Die Optimisten wrote: > Hello > > echo hello!# displays that, BUT: > echo "Hello!" # tells: > -su: !": event not found# this worked years before without problem! > Is that intended? These leads to

Re: bash Shell - escapes

'# I don't want to use " The short answer is... you can't. Quoting from the bash man page: "Enclosing characters in single quotes preserves the literal value of each character within the quotes. A single quote may not occur between single quotes, even when pre

Re: bash - shell events "!"

nd# this worked years before without problem! Is that intended? These leads to errors in many scripts (including installig package dkms) How can this be turned off? For me this behaviou should be changed, for example: Events should contain whitespace before or after it, or only work outside q

bash - shell events "!"

aviou should be changed, for example: Events should contain whitespace before or after it, or only work outside quoting... using GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)

bash Shell - escapes

On 2016-05-10 11:18, Die Optimisten wrote: Hi, How can I escape a ' inside '...' e.g. perl -e 'print '$ and a' '# I don't want to use " thank you Andrew I have to add, its bash - specific and PLEASE also CC: me using inform (AT) die-optimisten.net I'm not subscribed here THANKs

Re: systemd and bash scripts

Am 26.02.2016 um 17:42 schrieb tand.read: > dear debian supporters, > > I am testing my own systemd unit (a service) > > that has this [service] section: > Type=oneshot > > RemainAfterExit=yes > ExecStart=/root/bin/mytest.sh start > ExecStop=/bin/echo /root/bin/mytest.sh stop > > ("Want="-ed b

Re: systemd and bash scripts

a C program that merely execs you script. Something along the lines of #include int main(int argc, char *argv[]) { execl("/bin/bash", "/bin/bash", "/root/bin/mytest.sh", "start", (char *) 0); }

Re: systemd and bash scripts

" and > "active (exited)", but not a single line of the mytest.sh > script has run > > The only difference I see with ExecStart and ExecStop is that > the stop-one calls a binary (and works) while the start-one > calls a script (and goes to the bitbucket). Is the

Re: Increasing the number of bash history

I found in ~/.bashrc # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 Leaving this part alone, the result of history was also the same. That was not the case in wheezy. I've edited ~/.bashrc, so now $ cat ~/.bashrc ==omitting== HISTCO

Re: Increasing the number of bash history

With bash version 3 you can set to infinity the history size and size of history file of terminal edit file ~/.bashrc change HISTSIZE=1000 to HISTSIZE=-1 //history size of terminal change HISTFILESIZE=2000 to HISTFILESIZE=-1 //size of history file 2016-02-24 8:19 GMT-04:00 : > -BEGIN

Re: Increasing the number of bash history

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 24, 2016 at 08:16:01PM +0800, EenyMeenyMinyMoa wrote: > Hi, > I want to increase the number of bash history. > > $ history > ==omitting== > 1996 history > > After entering commands more than ten times, > I rel

Increasing the number of bash history

Hi, I want to increase the number of bash history. $ history ==omitting== 1996 history After entering commands more than ten times, I relaunched the terminal to see $ history ==omitting== 1996 history I've added the following lines to /home/eeny/.bashrc about a year ago. HISTSIZE=

Re: bash-completion, tab and ambiguous globs

On 2016-02-19 at 22:13, Chris Bannister wrote: > On Wed, Feb 17, 2016 at 10:14:06AM +0100, Nicolas George wrote: > >> Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit : >> >>> It can be creepily smart, like knowing the branches in your >>> project when you do git checkout bla or things

Re: bash-completion, tab and ambiguous globs

On Wed, Feb 17, 2016 at 10:14:06AM +0100, Nicolas George wrote: > Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit : > > It can be creepily smart, like knowing the branches in your project > > when you do git checkout bla or things like that. Not bad. > > You mean what zsh already did in

bash file completion seems to fail for perl -d but works for perl -wc

Hi; bash file completion seems to fail for perl -d but works for perl -wc This seems to be the case for Cygwin, Debian and Mac. Does anyone know how to add support for this or am I missing something simple? Thanks, Ken Wolcott

Re: bash-completion, tab and ambiguous globs

letion on which I had come to rely, so I always turn it off >> on my machines. > > By "turning off" bash-completion, do you mean uninstalling it or > something less radical ? It varies. In some cases I've uninstalled it, in other cases I've modified a config fi

Re: bash-completion, tab and ambiguous globs

ines. By "turning off" bash-completion, do you mean uninstalling it or something less radical ?

Re: bash-completion, tab and ambiguous globs

On 2016-02-18, The Wanderer wrote: > > I'm not sure I understand. How is this different from basic tab > completion, as opposed to the programmable completion which is provided > via the bash-completion package and is being discussed in this thread? > > I wouldn'

Re: bash-completion, tab and ambiguous globs

On 2016-02-17 at 12:43, Lisi Reisz wrote: > On Wednesday 17 February 2016 16:54:15 John L. Ries wrote: > >>> Seriously, when does bash-completion actually help someone on >>> the command line? The only time I notice it is when a pattern is >>> buggy and doesn&

Re: bash-completion, tab and ambiguous globs

On Wednesday 17 February 2016 16:54:15 John L. Ries wrote: > > Seriously, when does bash-completion actually help someone on the > > command line? The only time I notice it is when a pattern is buggy and > > doesn't let me complete a filename even when it's complet

Re: bash-completion, tab and ambiguous globs

Seriously, when does bash-completion actually help someone on the command line? The only time I notice it is when a pattern is buggy and doesn't let me complete a filename even when it's completely valid. It apparently doesn't do anything for you or me (but I'm a Korn shel

Re: bash-completion, tab and ambiguous globs

hings like that. Not bad. > > You mean what zsh already did in its default distribution fifteen years ago? > And, of course, without breaking the completion of globs. I don't know why you sound so... vindicative? Might be my ears. If bash-completions is too "fat" for me,

Re: bash-completion, tab and ambiguous globs

Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit : > It can be creepily smart, like knowing the branches in your project > when you do git checkout bla or things like that. Not bad. You mean what zsh already did in its default distribution fifteen years ago? And, of course, without break

Re: bash-completion, tab and ambiguous globs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 17, 2016 at 09:57:30AM +0100, Anders Andersson wrote: > On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas > wrote: > > In bash, typing, say, "ls x*y" then tab lists all the possible > > expansions of

Re: bash-completion, tab and ambiguous globs

On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas wrote: > In bash, typing, say, "ls x*y" then tab lists all the possible > expansions of "x*y" on the next line, then prints the command > line anew with "x*y" replaced by longest common stem. >

bash-completion, tab and ambiguous globs

In bash, typing, say, "ls x*y" then tab lists all the possible expansions of "x*y" on the next line, then prints the command line anew with "x*y" replaced by longest common stem. With bash-completion installed, "x*y" is summarily replaced by its first

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On Fri, 25 Sep 2015, Vincent Lefevre wrote: > On 2015-08-31 15:41:01 -0500, Don Armstrong wrote: > > For the record, lines starting with From are often escaped with > to > > avoid issues with mbox. So Vincent didn't purposefully prepend > to > > that. > > That's Debian's mailing-list software that

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-31 15:41:01 -0500, Don Armstrong wrote: > On Mon, 31 Aug 2015, David Wright wrote: > > Quoting Vincent Lefevre (vinc...@vinc17.net): > > > From the terminal point of view, the shell is just like another > > > process. > > > > Just to make it clear: I didn't write that, even though you'v

Re: bash script globbing

On Sun, September 20, 2015 3:28 pm, Loïc Grenié wrote: ... >> #!/bin/bash >> enscript --media=letter -2 --landscape --borders \ --header='$n|A.D. >> $D{%Y.%m.%d}|$* gmt | Page $% of $=' "$1" ... > Here "$1" means "for the first argument&quo

Re: bash script globbing

Hi, rlhar...@oplink.net wrote: > enscript --media=letter -2 --landscape --borders \ > --header='$n|A.D. $D{%Y.%m.%d}|$* gmt | Page $% of $=' "$1" > ... > when I execute >enscript+ * > in a directory containing several files, enscript prints only the first > file in the directory. This

Re: bash script globbing

2015-09-20 22:20 GMT+02:00 : > I have been using the following script (named "enscript+") as a substitute > for the package "a2ps": > > #!/bin/bash > enscript --media=letter -2 --landscape --borders \ > --header='$n|A.D. $D{%Y.%m.%d}|$* gmt |

bash script globbing

I have been using the following script (named "enscript+") as a substitute for the package "a2ps": #!/bin/bash enscript --media=letter -2 --landscape --borders \ --header='$n|A.D. $D{%Y.%m.%d}|$* gmt | Page $% of $=' "$1" The script works p

/usr/games not in PATH in TESTING (i3wm, BASH as default, using fish shell)

now since KDE in testing is in migration and a bit sketchy, and using SSCM as my login manager. My default shell is /bin/bash. The problem is, when logged in using SSCM, the PATH is only /bin /usr/bin /usr/local/bin. Seemingly, my /etc/profile, ~/.profile has not been run by the login program. I

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On Mon, 31 Aug 2015, David Wright wrote: > Quoting Vincent Lefevre (vinc...@vinc17.net): > > From the terminal point of view, the shell is just like another > > process. > > Just to make it clear: I didn't write that, even though you've made it > appear that I did by putting ">" in front of it. F

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Quoting Vincent Lefevre (vinc...@vinc17.net): > On 2015-08-21 22:08:33 -0500, David Wright wrote: > > Quoting Vincent Lefevre (vinc...@vinc17.net): > > > No, here's what I said: > > > > > > | In general, one wants NO-BREAK SPACE to be displayed just like > > > | a space. The differentiation is use

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-21 22:08:33 -0500, David Wright wrote: > Quoting Vincent Lefevre (vinc...@vinc17.net): > > No, here's what I said: > > > > | In general, one wants NO-BREAK SPACE to be displayed just like > > | a space. The differentiation is useful mainly in source code > > | and when editing, thus it

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

t; > . Q: How come i wrote a NO-BREAK SPACE in xterm+bash ? > > . A: I touched the key to the left of the space bar at the same time. > > . Fix: Redefine Alt-Space to type an ordinary space. > > > > Since then, the discussion moved on to how NBSP should be *displayed* i

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-21 08:36:43 -0500, David Wright wrote: > Quoting Erwan David (er...@rail.eu.org): > > 1) You're speaking input, Vincent was speaking output > > Eh? The OP was speaking input. To summarise, > . Q: How come i wrote a NO-BREAK SPACE in xterm+bash ? > . A: I t

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

t; Why not? Let's substitute TAB TAB for NBSP in your comment. > > My terminal happily swallows TAB TAB with cat > file, and renders > > it correctly with cat file. But when I type TAB TAB as shell input, > > I get "Display all 3402 possibilities? (y or n)". It s

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-21 07:30:18 +0200, Erwan David wrote: > On Fri, Aug 21, 2015 at 04:56:54AM CEST, David Wright > said: > > Quoting Vincent Lefevre (vinc...@vinc17.net): > > > On 2015-08-19 16:33:09 -0500, David Wright wrote: > > > > Quoting Thomas Schmitt (scdbac...@gmx.net): > > > > > But the typograp

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On Fri, Aug 21, 2015 at 04:56:54AM CEST, David Wright said: > Quoting Vincent Lefevre (vinc...@vinc17.net): > > On 2015-08-19 16:33:09 -0500, David Wright wrote: > > > Quoting Thomas Schmitt (scdbac...@gmx.net): > > > > But the typographical purpose of NO-BREAK SPACE is to look > > > > like space

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Quoting Vincent Lefevre (vinc...@vinc17.net): > On 2015-08-19 12:55:39 -0500, David Wright wrote: > > Quoting Vincent Lefevre (vinc...@vinc17.net): > > > In general, one wants NO-BREAK SPACE to be displayed just like a space. > > > > Why would I want a character that doesn't behave as a space to b

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Quoting Vincent Lefevre (vinc...@vinc17.net): > On 2015-08-19 16:33:09 -0500, David Wright wrote: > > Quoting Thomas Schmitt (scdbac...@gmx.net): > > > But the typographical purpose of NO-BREAK SPACE is to look > > > like space without inviting an automatic line break. > > > So making it look not l

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-19 16:33:09 -0500, David Wright wrote: > Quoting Thomas Schmitt (scdbac...@gmx.net): > > But the typographical purpose of NO-BREAK SPACE is to look > > like space without inviting an automatic line break. > > So making it look not like space would be absurd. > > But shell input is not a

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-19 12:55:39 -0500, David Wright wrote: > Quoting Vincent Lefevre (vinc...@vinc17.net): > > In general, one wants NO-BREAK SPACE to be displayed just like a space. > > Why would I want a character that doesn't behave as a space to be > displayed as a normal space? (For example, in the sh

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 08/20/2015 01:59 AM, Bonno Bloksma wrote: Hi, In general, one wants NO-BREAK SPACE to be displayed just like a space. Why would I want a character that doesn't behave as a space to be displayed as a normal space? (For example, in the shell, as in the OP's original question.) It seems a re

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 20/08/15 06:59, Bonno Bloksma wrote: If you are talking about console use, indeed I would not know why I would want / need it there. Because you might be using your terminal to edit an input file for a document processing system which contains the character, or to create new files that co

RE: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Hi, >> In general, one wants NO-BREAK SPACE to be displayed just like a space. > > Why would I want a character that doesn't behave as a space to be displayed > as a normal space? (For example, in the shell, as in the OP's original > question.) > It seems a recipe for confusion at best, and for

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

st. > > It's name should be Spoof Space. On an UTF-8 terminal it > travels with Copy+Paste and survives in bash history. > > Imagine my initial panic when my few weeks old Debian told me > that there is no '..' in an ext4 directory. This is my beef. But I move

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

; and for exploits at worst. It's name should be Spoof Space. On an UTF-8 terminal it travels with Copy+Paste and survives in bash history. Imagine my initial panic when my few weeks old Debian told me that there is no '..' in an ext4 directory. Have a nice day :) Thomas

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Quoting Vincent Lefevre (vinc...@vinc17.net): > On 2015-08-11 14:22:23 +0200, Thomas Schmitt wrote: > > i wrote: > > > > Mine is a US QWERTY. Two "Alt" keys, no "AltGr". > > > > Vincent Lefevre wrote: > > > It is written "Alt" on US keyboards, and "Alt Gr" on US-International > > > and non-US keyb

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-11 14:22:23 +0200, Thomas Schmitt wrote: > Hi, > > i wrote: > > > Mine is a US QWERTY. Two "Alt" keys, no "AltGr". > > Vincent Lefevre wrote: > > It is written "Alt" on US keyboards, and "Alt Gr" on US-International > > and non-US keyboards. > > As X events mine are distinguished as A

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Hi, i wrote: > > Mine is a US QWERTY. Two "Alt" keys, no "AltGr". Vincent Lefevre wrote: > It is written "Alt" on US keyboards, and "Alt Gr" on US-International > and non-US keyboards. As X events mine are distinguished as Alt_L and Alt_R. (After all the translation stories i am not sure whether

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

useful. > Having the choice between totally invisible, but not empty > Alt+Spacebar plus beeping Alt+keys on the one hand, > and visible Alt+keys "±²³´µ¶·¸¹°­½ñ÷åòôùõéïðÛÝÜáóäæçèêë컧úøãöâîí¬®¯" > plus a real blank as Alt+Spacebar, on the other hand, i choose > the latter. Th

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On Sun, Aug 09, 2015 at 12:39:32PM +0200, Nicolas George wrote: > Next The Onion headline: a disgruntled Debian user opens fire at a X.org Is that some sort of American reference? -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the pe

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Hi, > Well, it seems that there's some confusion. By "Alt", I meant the > ISO_Level3_Shift key, which is bound to the physical Alt and AltGr > keys in my keyboard configuration. Mine is a US QWERTY. Two "Alt" keys, no "AltGr". https://en.wikipedia.org/wiki/Template:Keyboard xkbdcomp reports it

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Quoting Vincent Lefevre (vinc...@vinc17.net): > On 2015-08-10 13:02:07 +0200, Thomas Schmitt wrote: > > Vincent Lefevre wrote: > > > On my Debian/unstable machine, Alt-space gives a normal space in > > > xterm. There must be something else in the user's config. > > > > Do you have any "Translation

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-10 13:02:07 +0200, Thomas Schmitt wrote: > Vincent Lefevre wrote: > > On my Debian/unstable machine, Alt-space gives a normal space in > > xterm. There must be something else in the user's config. > > Do you have any "Translation" among the xterm resources ? > > appres XTerm | fgrep

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Hi, Vincent Lefevre wrote: > On my Debian/unstable machine, Alt-space gives a normal space in > xterm. There must be something else in the user's config. Do you have any "Translation" among the xterm resources ? appres XTerm | fgrep ransl yields on my machine only my individual workaround

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-09 14:24:44 +0200, Nicolas George wrote: > In other words, at the XKB level, the space key is the most boring key > ever. The conversion to non-break-space happens because of XTerm or its > libraries. On my Debian/unstable machine, Alt-space gives a normal space in xterm. There must be

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Le duodi 22 thermidor, an CCXXIII, Thomas Schmitt a écrit : > I guess Alt+Spacebar is about > > interpret Alt_L+AnyOf(all) { > virtualModifier= Alt; > action= SetMods(modifiers=modMapMods,clearLocks); > }; I do not think so. IIUC, it means that Alt_L enables the Alt virtua

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Hi, Nicolas George wrote: > I suppose everybody already knows this, but to check what keys applications > receive from the X11 server, the xev program can be of great help. Praise xev. > xkbcomp $DISPLAY - Nothing conclusive to see about "space" or "SPCE". > The xkb_types section defines type

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

On 2015-08-09 12:39:32 +0200, Nicolas George wrote: > If everything was not already complicated enough, shift, control and > caps-lock have each a fixed value in the state mask, but all the other > modifiers (from num-lock to alt-gr, including meta and super) arrive to the > application as mod1 to

Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

Le duodi 22 thermidor, an CCXXIII, Thomas Schmitt a écrit : > Still trying to grok the xkb stuff, i get the impression > that at least on my system xterm gets to see Alt+Space, not a > "nobreakspace" produced by general keyboard translations. I suppose everybody already knows this, but to check wh

<    4   5   6   7   8   9   10   11   12   13   >