There is an answer from SuperUser , which renames filenames containing whitespace: for f in *\ *; do mv "$f" "${f// /_}"; done The part I don't understand is *\ *. The author wrote that: > *\ * selects all files with a space in their name as input for the the for loop. The pattern *X* selects all files with X in their name, and for the special character space, we have to escape it with a slash so that bash doesn't treat it as separating different arguments. Since * does not match a space, why does *\ * also match files with multiple space character when it only has one space in it?

How can I remove special non-characters e.g. faces, avatars, emojis, symbols that are not part of national alphabets from filenames while keeping any national alphabets intact? e.g. myfilename_hhjs_φφφδσε2_五(wǔ)__😎💃🏻 I want this result: e.g. myfilename_hhjs_φφφδσε2_五(wǔ)__ The faces may are vary as well their position. I want Greek or Chinese or whatever national alphabet characters to remain intact.

I need to create a file named *'test'* If I write touch \'test\' ls shows 'test' But if I write touch \*\'test\'\* ls now shows *'\''test'\''* What's the trick ? Can someone explain me what I did wrong ? My OS is Ubuntu 20.04

I have a script that sends out email to sysadmin group when a server is powered on or off. The email contains dump of some important logs like /var/log/messages, /var/log/secure, /var/log/boot.log . The /var/log/boot.log contains some special characters which when sent in email looks garbled as it contains some special formatting chars for coloring and tabs. How do I remove these special characters to make it readable? I know I can use sed to remove the characters but I am looking for an easy and elegant solution. (The /var/log/boot.log is from CentOS 6.x) Here's a dump of my /var/log/boot/.log: [root@vagrant ~]# cat -v /var/log/boot.log ^[%G Welcome to ^[[0;36mCentOS^[[0;39m ^M Starting udev: ^[%G^[[60G[^[[0;32m OK ^[[0;39m]^M^M Setting hostname vagrant: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Setting up Logical Volume Management: 5 logical volume(s) in volume group "vgdynamic" now active^M 3 logical volume(s) in volume group "vgstatic" now active^M ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Checking filesystems^M /dev/mapper/vgstatic-lvroot: clean, 8102/884736 files, 175959/3537920 blocks^M /dev/sda1: clean, 44/32768 files, 17226/131072 blocks^M /dev/mapper/vgdynamic-lvhome: clean, 10280/196608 files, 74141/786432 blocks^M /dev/mapper/vgdynamic-lvopt: clean, 932/655360 files, 104046/2620416 blocks^M /dev/mapper/vgstatic-lvtmp: clean, 12/131072 files, 25386/524288 blocks^M /dev/mapper/vgstatic-lvusr: clean, 41785/262144 files, 236524/1048576 blocks^M /dev/mapper/vgdynamic-lvvar: clean, 1989/393216 files, 93057/1572864 blocks^M /dev/mapper/vgdynamic-lvvarlog: clean, 55/49152 files, 8030/196608 blocks^M /dev/mapper/vgdynamic-lvaudit: clean, 14/65536 files, 73366/262144 blocks^M ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Remounting root filesystem in read-write mode: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Mounting local filesystems: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Enabling /etc/fstab swaps: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Entering non-interactive startup^M Calling the system activity data collector (sadc)... ^M Starting monitoring for VG vgdynamic: 5 logical volume(s) in volume group "vgdynamic" monitored^M ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting monitoring for VG vgstatic: 3 logical volume(s) in volume group "vgstatic" monitored^M ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Bringing up loopback interface: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Bringing up interface eth0: ^M Determining IP information for eth0... done.^M ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting auditd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting system logger: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting lwsmd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^[[60G[^[[0;32m OK ^[[0;39m]^M^M Mounting filesystems: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Retrigger failed udev events^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting the VirtualBox Guest Additions ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting VirtualBox Guest Addition service ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting sshd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting ntpd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting crond: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M Starting atd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^M [root@vagrant ~]#

I am trying to SSH to Linux box with username containing /. For example: tes/t But the characters after / get truncated and user is seen as tes during SSH. SSH then fails with this user since its invalid. Even the audit log in the machine shows user as tes. **Note:** * I have configured the user as tes/t with valid permissions and the same is seen in database also. * I am using Ubuntu 22.04 Any idea where these session find the truncated version? sh Log:

sshd: info Failed password for tes from 10.120.64.33 port 56498 ssh2

audit.log: 
15:09:17.305Z [tes]: Login_Denied - - apparently_via=Remote ip=10.120.64.33 auth=PAM In

Is there any special bash reserved characters in bash regex expression? - ex: - eg: `if [[ $url =~ ^https:\/\/www\.youtube\.com\/playlist\?(.+&)?list= ]]; then echo "URL matches the regex"; fi` \ This is just a normal regex test. - problem: - Do I need to be careful about special case where: \ I have things like eg: **%VAR%, $VAR, &VAR, (or any potential special bash reserved characters)**, inside my regex expression. \ Do I need to **escape** those? - eg: `if [[ $url =~ ^https:\/\/%VAR%/$VAR/&VAR/!@#$%^&*()-=_+/wte;/ ]]; then echo "URL matches the regex"; fi` \ // assume I intentionally need to match such regex - ex: - for example, I know that **' or "** certainly have special meanings when they are at the ends. - https://stackoverflow.com/questions/218156/bash-regex-with-quotes - eg: `if [[ $url =~ '^https:\/\/www\.youtube\.com\/playlist\?(.+&)?list=' ]]; then echo "Screw up"; fi` - again: - I am **not** asking about escaping the **regex** (I know how to use regex, be it PCRE or ERE doesnt matter.) - I am asking about escaping **the bash reserved special characters**, when inside a regex expression, if there is any. - In another words, is the regex expression in bash - more like /^http:\/\/www/g in js literal regex, where the inside will always be literal regex; - or more like "^http:\\/\\/www" in js RegExp, where you need to escape the reserved characters `' " \`` etc due to being inside a string --- _**Update**_: - For "Is there any special bash reserved characters in bash regex expression?" \ The simple answer is yes. - As for an example:

url="https://www.youtube.com/playlist?list=PLmHVyfmcRKyxvxehq3fiGjKDsEyy6d4Tz "
  regex='^https:\/\/www\.youtube\.com\/playlist\?(.+&)?list='
  
  idx=0
  (( idx++ )) # normal
  if [[ $url =~ ^https:\/\/www\.youtube\.com\/playlist\?(.+&)?list= ]]; then echo "URL matches the regex - $idx"; fi
  (( idx++ )) # normal
  if [[ $url =~ $regex ]]; then echo "URL matches the regex - $idx"; fi
  (( idx++ ))
  yt='www\.youtube\.com\/'
  if [[ $url =~ ^https:\/\/${yt}playlist\?(.+&)?list= ]]; then echo "URL matches the regex - $idx"; fi
  (( idx++ ))
  if [[ $url =~ ^https:\/\/'${yt}'playlist\?(.+&)?list= ]]; then echo "URL matches the regex - $idx"; fi
  (( idx++ ))
  if [[ $url =~ '^https:\/\/'${yt}'playlist\?'(.+&)?list= ]]; then echo "URL matches the regex - $idx"; fi

--- ***Update***: For what literal regex that I want means:

text='The pizza is 2'\'' and 100$price' # The pizza is 2' and 100$price

# literal regex I want: [0-9]+' and [0-9]+\$price
regex="[0-9]+' and [0-9]+\\\$price"
if [[ "$text" =~ $regex ]]; then echo "this is the normal way of doing things, do you see I need to escape the \ & $ ?"; fi
# if [[ "$text" =~ [0-9]+' and [0-9]+\$price ]]; then echo "this is what I prefer to have -- literal regex, like / /g in js. But this wont even compile"; fi

js anology:

const str = "The pizza is 2' and 100$price";

if (/[0-9]+' and [0-9]+\$price/.test(str)) {
  console.log('literal regex');
}
if (new RegExp("[0-9]+' and [0-9]+\\$price").test(str)) {
  console.log('non literal regex');
}

- ***conclusion from comments & discussions***: - use ' single quote & a variable outside the if statement. - here, ' in bash is actually analogous to / in js - _-- so, the literal regex I mean (should have learnt more before asking.) \ (you may read comments & discussions below)_ - though, escaping single quote ' in bash -- `'\'', is not as pretty as escaping / in js -- \/`.)

I'm having trouble finding a name for the - character in the context of a piped bash command. 1. What is the - character called? 2. Can I replace it with something more readable for a script? Example command:

echo -ne "my command" | socat - /dev/somefile

I want to output some text with tab as separator using ansible here's task snippet - name: Create output file blockinfile: block: | Some text\tmore text path: '{{ playbook_dir }}/output.txt' create: true CURRENT OUTPUT # BEGIN ANSIBLE MANAGED BLOCK Some text\tmore text # END ANSIBLE MANAGED BLOCK DESIRED # BEGIN ANSIBLE MANAGED BLOCK Some text more text # END ANSIBLE MANAGED BLOCK

so I wanted to write a script to replace special characters with their escaped equivalent so I can pass it to mkdir command. As a friend used a similar line I can use this to replace parantheses with underline like below: echo 'Hello (World)' | sed 's/(\|)/_/g' but when I changed it to below command the output is not what I desire echo 'Hello (World)' | sed 's/(\|)/\(\|\)/g' system output: Hello (|)World(|) my desired output: Hello \(World\) any way to do this? I used other people's suggestions like using "tr" command but couldn't get the desired output from that either.

$ bash --version
GNU bash, versione 5.2.26(1)-release (x86_64-pc-linux-gnu)

I don't know how to deal with *$VAR* when its value inside contains single quote (') and/or backtick (

`

). I'm in the need of executing *find*'s -exec based on entries found in list.txt. list.txt contains: - one *FILENAME.EXT* per line - each line ends with *newline* (\n) As a preventive test to verify everything is OK, I run these:

$ while IFS= read -r song; do find /mnt/EXTHDD/unsorted -type f -name "$song"; done < list.txt

$ while IFS= read -r song; do find /mnt/EXTHDD/unsorted -type f -name "*$song*"; done < list.txt

$ while IFS= read -r song; do find /mnt/EXTHDD/unsorted -type f -name '$song'; done < list.txt

$ while IFS= read -r song; do find /mnt/EXTHDD/unsorted -type f -name "${song}"; done < list.txt

None worked... Unfortunately, not all occurrences are listed due to Special Characters in *FILENAME* and thus $song variable cannot be quoted correctly (neither with double quotes, nor single quotes). Example of lines *FILENAME.EXT* found in list.txt:

Pino Daniele ~  Napule' - Raccolta completa ~ 01.14) O ssaje comme fa `o core.mp3

[CONCERTI] Malora -- Live@TANTE'! (Agosto '05, Villa Fossa [presa diretta, mixer:stereo]) -- #15. 20:30 ... Tutto tace?.wave

Why would a file show up surrounded by double quotes with a character surrounded by single quotes within it? "insight_automation.log'.'2024-03-13" I am using Ubuntu Server 22.04.3 LTS. A service desk management program (Atlassian Jira Data Center 9.12.4 if that is relevant) installed on the server writes to various log files. Some of the files are rotated, and after an update some of the log files display as shown above when I execute ~$ ls /var/[application-directory-path]/log Other log files display without any quotes. Some examples: atlassian-jira.log atlassian-jira.log.1 insight_audit.log insight_audit.log.2024-03-05 insight_automation.log There are many posts about single and double quotes in Unix systems, especially with the GNU developers adding single quotes around files with spaces. I am somewhat familiar with the nuance surrounding these characters and Unix, but this is new to me, and I can't find an explanation anywhere online (likely because it is difficult to phrase the problem). I looked at the logging configuration files and nothing appears different between the delinquent *insight_automation.log* rotate settings and the other log files. My only guess is that the dot in the name is a different Unicode character that is escaped similar to the way spaces in file names are. Maybe One Dot Leader, Interpunct, or Bullet? I am sure I can fix the issue simply, but knowing why it is displayed like this would help a lot.

I have a DE_CopyOldToNew.sh file that was created in Windows. The file is then uploaded to Linux using WinSCP. The file contains a whole bunch of cp commands that copies files to a new folder with a new filename being assigned. The commands contain folders and files with diacritics like Gewährleistungsbürgschaft. When I do a cat DE_CopyOldToNew.sh I noticed that the diacritics are displayed in a "corrupted" way like Gew▒hrleistungsb▒rgschaft. When I do a view DE_CopyOldToNew.sh then the diacritics are displayed as they should be, like Gewährleistungsbürgschaft. When I execute my script I am getting cp: cannot stat errors and the diacritics in the folders and files are displayed as Gew\344hrleistungsb\374rgschaft. I have uploaded the file using binary as well as text and I have also performed a dos2unix DE_CopyOldToNew.sh. When I copy the content of my script in Windows and paste it into a new file in Linux then I am able to run the new script without issues. What is causing the uploaded version to be "corrupted" (for a lack of a better word)?

I am using a US keyboard layout because it's more convenient for programming, but since I am German I need the German umlauts for texting. (Umlauts like ÄäÖöÜü) I am running Manjaro with KDE. I want to get press AltGr + u -> ü and AltGr + Shift + u -> Ü I tried copying the US keymap from /usr/share/kbd/keymap and adding

alt keycode 32 = odiaeresis

to get the ü to work, but it didn't do anything. I queried the keycode 32 by entering

xmodmap -pk | grep -i o

which returned:

32         0x006f (o)      0x004f (O)      0x006f (o)      0x004f (O)

I need to insert tab character on place of _ between day and hour. exiftool -T -r -filename -CreateDate -d "%Y%"."%m%"."%d_%H%"."%M%"."%S" /Users/***/***/testmapa/mapa2/ > /Users/***/***/testmapa/out10.csv I have tried to insert it in all possible ways with \t, in combination with "",'',& and no collapse. It just wont work for me. Im using osx terminal. Take note that line is in .Command file. Not terminal itself. Edit; my solution was ## and | perl -pE 's/##/\t/g'

After upgrading ubuntu to 22.04 I wasn't able to login because my password has any accented vowel, as for example "ú". This happens ONLY the FIRST login. In my case the new ubuntu 22.04 does NOT accept accented vowels in the user password when entered directly from keyboard, but this behaviour is ONLY at the FIRST login. The workaround for me was to enter that character by the on-screen keyboard and the others from normal keyboard. Once the password has been accepted and I get access, then the system does accept my password directly from keyboard as normal and at any other time. I tested it: I tried to enter it directly from keyboard in a terminal and it worked, and I tried to suspend system and then enter password from keyboard directly and then it worked. So, the problem entering my password is only at the begin login, it's only then when I am in the need to enter that character of my password from an on-screen keyboard. Anyway, I think this is NOT the properly working way that ubuntu is supposed to, as in every older versions a password with an accented vowel worked ok typed directly from the normal keyboard. So please, notify to the appropriated person to fix this. Thanks in advance.

I'm on a Mac keyboard and I would prefer to have special characters available similar or the same to how they are accessed in OS X/macOS. [Here](https://superuser.com/q/814843/57016) is a similar question for Windows. E.g., alt+e+e → é and alt+c → ç without any GNOME Compose key funkiness. Is there any tool that provides this function? Or is this something that should be changed in some possibly outdated Mac keyboard layout settings? If the latter, how would I resolve conflicts with existing alt+letter shortcuts (both in identifying the conflict and working around them), e.g., would the alt+letter shortcut do both the shortcut and produce the special character? Are there any patent conflicts or intellectual property reasons to not duplicate this function?

What's the name for the *.* symbol and what is its significance?

I'm using Devuan GNU/Linux Daedalus, with Cinnamon 5.6.7 (Xorg server 21.1.7). I want to type in some characters not available on my keyboard, nor (to my knowledge) in my keyboard layout (English - English (US); and also sometimes Hebrew - Hebrew). I know I can get them using the charmap application, but I'd really rather type and not use the mouse, switch focus etc. Can I do this? How? Notes: * I use all kinds of apps, but for the sake of discussion let's focus on entering text in text areas/boxes in Nemo (the file explorer), cinnamon dialog boxes, text editors like gedit and mousepad, and Firefox text areas/boxes. * I'm most interested in Latin-ish characters from the "Latin Supplementary" Unicode block, such as: §, ±, · and others; so if your answer only regards those it's still valid.

>Many questions like 'How to type the double-quote char (")?' are being asked, and we don't want to clutter our community with the same answer (Type it as \" if not enclosed in 's, " if enclosed in 's.) So, the question is here. You can't type special chars into a terminal like normal ones, e.g. this command will fail: echo Updates (11) So, how to type in these chars in the terminal as if they were normal ones? !#$^&*?[](){}~;'"\|

I use _Debian SID_ and the **Terminator** is my terminal emulator. After updating the system the last time (yesterday 2023/11/22) and rebooting, some characters in my terminal in certain commands are showing strange characters. However, in the same terminal, connected via SSH to Arch Linux, the same commands run without the problem: EDIT 1: I recorded my screen showing the entire problem process and it is at this [LINK](https://imgur.com/htELY7S) (maximize the video for better viewing). Anyway, I'll describe it step by step: 1. _With terminator open..._ 1. **Split** horizontally (terminator) 1. **Back** to the panel above (terminator) 1. **Split** vertically (terminator) 1. **Go back** to the panel on the left (terminator) 1. Print the variable $TERM: xterm-256color 1. I run htop: it has strange characters 1. **Go** to the panel on the right (terminator) 1. Print the variable $TERM: xterm-256color 1. I run ranger: it has strange characters 1. **Go** to the panel below (where I will make the SSH connection) (terminator) 1. Print the variable $TERM: xterm-256color 1. I connect to the remote host (Arch Linux which is on the local network) via SSH 1. Print the variable $TERM: xterm-256color 1. I run htop: **NOT** has strange characters 1. Close htop 1. I run ranger: **NOT** has strange characters 1. Close the ranger 1. **I join** a tmux session 1. Print the variable $TERM: tmux-256color 1. **Split** vertically (tmux) 1. **Go back** to the left panel (tmux) 1. I run htop: **NOT** has strange characters 1. **Go** to the panel on the right (tmux) 1. Print the variable $TERM: tmux-256color 1. I run ranger: **NOT** has strange characters Can anyone help?