alacritty | A cross-platform , OpenGL terminal emulator | Command Line Interface library

strace can attach to a process using -p:

From your code and the output on your system, it appears that:

• type char has indeed 8 bits. Its size is 1 by definition. char **argv is a pointer to an array of pointers to C strings, null terminated arrays of char (8-bit bytes).
• the char type is signed for your compiler configuration, hence the output 0xFFFFFFE7 and 0xFFFFFFE0 for values beyond 127. char values are passed as int to printf, which interprets the value as unsigned for the %X conversion. The behavior is technically undefined, but in practice negative values are offset by 2³² when used as unsigned. You can configure gcc to make the char type unsigned by default with -funsigned-char, a safer choice that is also more consistent with the C library behavior.
• the 2 non ASCII characters çà are encoded as single bytes E7 and E0, which correspond to Microsoft's proprietary encoding, their code page Windows-1252, not UTF-8 as you assume.

The situation is ultimately confusing: the command line argument is passed to the program encoded with the Windows-1252 code page, but the terminal uses the old MS/DOS code page 437 for compatibility with historic stuff. Hence your program outputs the bytes it receives as command line arguments, but the terminal shows the corresponding characters from CP437, namely τ and α.

Microsoft made historic decisions regarding the encoding of non ASCII characters that seem obsolete by today's standards, it is a shame they seem stuck with cumbersome choices other vendors have steered away from for good reasons. Programming in C in this environment is a rough road.

UTF-8 was invented in September of 1992 by Unix team leaders Kenneth Thomson and Rob Pike. They implemented it in plan-9 overnight as it had a number of interesting properties for compatibility with the C language character strings. Microsoft had already invested millions in their own system and ignored this simpler approach, which has become ubiquitous on the web today.

Despite the fact that emsdk is installed, following current (as at 8 Jan '22) documentation will not result in working examples. Build would be failed.

In order to build it on Ubuntu with make --version GNU Make 4.2.1 you need to provide -e option to pass environment variables to make

Then, after build is finished -- start python http server in examples directory and navigate to it in browser: python3 -m http.server 9999 open localhost:9999 and open desired example.

Since crates can be compiled with or without certain features which result in different code, there isn't any mechanism to up- or download pre-compiled crates. On top of that, the list of supported targets is very long which would make it very likely that the platform you're on doesn't have pre-compiled binaries.

Finally, there'd need to be additional mechanisms to sign the code and verify that the pre-compiled code matches the source code.

So all in all there are several obstacles that render implementing this impractical.

The alacritty terminal emulator usually goes with the $TERM variable set to alacritty (instead of xterm or xterm-256color or a variant.)

So assuming that's your configuration (you might be getting the incorrect $TERM setting, particularly if you're connecting to a remote box through SSH, or using a multiplexer such as tmux or screen), you can use that in your vimrc to check whether you're running in Alacritty.

You can check that from the shell:

So you want to print the first 'Name=' but not the second one ? If it is what you are trying to do, just break the loop after printing the first 'Name='

alacritty -e will run a Linux command and you are giving it a function as an argument so it will not work.

The only way to make it work is splitting it into two scripts. I called them echo.sh and function.sh.

echo.sh

I think pressing command + N does the trick