The unwanted behavior was noted while splitting the string from
shell-command-to-string using the newline character as a seperator.
Long lines printed on one line in the terminal were splitted (I was
using "calibredb list" that is part of the CLI of the calibre ebook
Now I noticed that shell-command-to-string just uses the command
process-file, which on its turn just uses call process.
Therefore I tried the following command:
(call-process "calibredb" nil t nil "list").
I noticed that lines supposed to be single lines (they are printed
on single lines in e.g. gnome-terminal if the window is sufficiently
wide), were splitted on 80 chars length (of course you could try
any other command that outputs lines that are longer than 80 chars).
I assume that this is undesirable behavior as I would prefer Emacs to
treat single lines as single lines. I could not find where the length
of 80 is defined (no info online and no info in the documentation), but I guess it is defined in the C code.
In GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.13,
cairo version 1.16.0)
of 2020-03-28 built on daniel-fedora
Windowing system distributor 'Fedora Project', version 11.0.12008000
System Description: Fedora release 32 (Thirty Two)
Error retrieving kernelspecs: (json-readtable-error 76)
Loading ‘mma’: unescaped character literals `?(', `?)' detected!
Created zotero link.
Loading /home/dalanicolai/.my_emacs.d/init.el (source)...done
For information about GNU Emacs and the GNU system, type C-h C-a.
Making completion list...
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: @im=ibus
Major mode: Fundamental
Minor modes in effect: