[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vp / vr / w / wg / wsg / wsr / x / y ] [Home]
4chanarchives logo
Blink and Beep Doesn't Work on Linux Shell Anymore
Images are sometimes not shown due to bandwidth/network limitations. Refreshing the page usually helps.

You are currently reading a thread in /g/ - Technology

Thread replies: 32
Thread images: 1
File: Hashbang.jpg (18 KB, 528x528) Image search: [Google]
Hashbang.jpg
18 KB, 528x528
/g/entlemen,

I have a question: Anyone know why blink or beep doesn't work anymore in the modern versions of shell (Bash, in the actual distros)?

Thank you in advance.
>>
>>55363455
It works fine in bash. The problem is that 99% of distros no longer load the actual beep module.

You need to manually load the module and then beep will work.
>>
>>55363502
Thank you by your answer about the beep problem. I will investigate.

And, by the way, do you know about the blink problem too? Like:

echo  -e "\033[5mBlinking text\033[0m"


doesn't work anymore in Bash.
>>
>>55363554
bump
>>
>>55363455
>blink or beep
First thing I get rid of in a new install.
OP is some kind of hyperfag
>>
>blink and bleep
The language you Linuxfags use confuses me more and more every day
>>
>>55363455
I think I found my (partial) answer about the blink problem in shell:

It doesn't work on gnome terminal (still don't know why). I switched to xterm and it works fine.

Thank you everyone in advance.
>>
>>55363909
"sowy" :D
>>
>>55363910
check if there's an option that filters it out
>>
>>55364136
Thank you. I'm trying to find it too.
>>
>>55363910
>It doesn't work on gnome terminal (still don't know why).
Weird, it works in my Gnome Terminal, yet , there's no setting for it. Never noticed that before.
>>
>>55363455
Linux has not shell, retard.
(Will /g/ ever learn?)
>>
>>55365893
And you can it (Bash) what?
>>
>>55365678
Mysterious problems that only a no-end number of Linux distributions can bring to you. Caos always come in tiny pieces, bit by bit :D
>>
>>55363455
Because they're annoying as fuck, mainly, so most distros and terminals default them off.
>>
>>55363554
bash isn't the terminal you fucking idiot
>>
>>55366118
And you call it (Bash) what? (sorry for the previous error)
>>
>>55363909
>blink and bleep
>fizzbuzz
>ganoo slash leenucks
>grub
>feh
>sudo pacman

Linux language.
>>
>>55366247
Considering you NOT a Troll (and you don't understand all the conversation above) I will answer (shortly) your question:

Shell -> Bash, sh, csh, zsh (and so on)
Terminal (emulations) -> Gnome terminal, xterm, uxterm (and so on)

And to all /g/entlemen

What you think about Xon.sh? Its written in Python. Anyone already tested it?
>>
>>55366313
I think you responded to the wrong person?
>>
>>55366330
Sorry /g/entlaman. A lot of work here and I made some mistakes (and a lot of typing errors too) :D
>>
>>55366378
And seeing it now I think it really was for you. But I will redact it:

I think when I talk about Bash it was implicit I was talking about using Bash through a terminal emulation. I just short things out. Sorry for the misunderstanding.
>>
>>55366460
But bash literally has nothing to do with it. You could run any shell you want, or even no shell at all. It wouldn't influence your terminal's ability to render blinking text or not...

Why even mention bash? It's useless information that neither describes your problem nor brings you closer to a solution. Why not just name the terminal instead?

Like,
>And, by the way, do you know about the blink problem too? Like:
>
echo  -e "\033[5mBlinking text\033[0m"

>doesn't work anymore in INSERT_TERMINAL_EMULATOR_HERE.
would have been a perfectly valid post

but instead of posting the only relevant thing, you go ahead and show signs of general confusion around all things terminal. What the hell?
>>
>>55366638
He's gotta learn somehow anon, and if he doesn't wanna read documentation on anything, he may as well be forced to see any misconceptions that he may have.
>>
>>55366638
I don't think it was a confusion on any level. I was trying to figure out a problem and I was thinking the same could be on Bash (and not on the terminal per se). I found out a clue about the real problem (and the real troubleshooting direction) in a cross search long after I start the thread, in a topic about ncurses:

http://unix.stackexchange.com/questions/151673/attrona-blink-using-ncurses-does-nothing

Don't assume people will always know what to do, or what to point out to the correct path from the start before try for help to better understand the problem. And I think I was fortunate enough to find out this clue in the middle of our discussion in this thread. After all I didn't stop to try to search (in parallel) an answer even in the middle of this conversation.
>>
>>55366817
Have you tried googling “<name of terminal emulator> blinking text”?

like

https://encrypted.google.com/search?hl=en&q=urxvt%20blinking%20text
or
https://encrypted.google.com/search?sclient=psy-ab&hl=en&btnG=Search&q=gnome-terminal+blinking+text
>>
Continuing from >>55366817

Google has all the answers... but we need to know how to ask first :^)

>>55366752

Yes, as I describe it in >>55366817

Thank you by your consideration.
>>
>>55366879
although note that 9 out of 10 results you find will be about people asking how to disable it
>>
Try searching in Google:

"blinking text issues + TERMNAME + ncurses + DISTRO"

No quotes.
>>
>>55366928
Leave the all the + signs there as well.
>>
>>55366879

I'm working on it right now :) I'll try to find out if it is a:

1 - problem or;
2 - configuration or;
3 - limitation

in the Gnome terminal, as I will try to find out too if it is a matter of version, distribution, and so on.

Than you anon.

And as I said before, I'm in the middle of my work and things can take some time to achieve in this search, but I (hope) will find out about this "issue" a.s.a.p..

>>55366893

Ouch... Thanks by the tip anon.
>>
>>55366928
>>55366959

Thank you anon.
Thread replies: 32
Thread images: 1

banner
banner
[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vp / vr / w / wg / wsg / wsr / x / y] [Home]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
If a post contains personal/copyrighted/illegal content you can contact me at [email protected] with that post and thread number and it will be removed as soon as possible.
DMCA Content Takedown via dmca.com
All images are hosted on imgur.com, send takedown notices to them.
This is a 4chan archive - all of the content originated from them. If you need IP information for a Poster - you need to contact them. This website shows only archived content.