Post your handy utility scripts!

General system Community contributions
82

I should have known about the testing environment! I’ll try to figure out how to get hold of it, get it running. I deserves wider distribution! Thanks for the goodies…

83

See the gitlab link above. It’s easy to compile it, the entire source code is just one .cpp file. Just download the file, and run the command to compile it in the directory where you put it… It should take 1 second or so. Make sure to have ImageMagick installed, before you try it, or it won’t work. :frog:

84

Saw it - just have to figure out best way to acquire from it (haven’t done that much :blush: )

85 
git clone git@gitlab.com:Kresimir235/fay-terminal-image-rasteriser.git

Nah, it can do only FROGGE, just tested it. :frog:

image
image1175×768 229 KB

P.S. Cool retro FROGGE

Screenshot_20210515_213447
Screenshot_20210515_2134471392×938 262 KB

It has DYEURS COLOURS!!!1111 :scream:

2 Likes
86

@Kresimir can’t get it to work in Alacritty or Konsole, what am I doing wrong?

87

hmm, my yay must be broken…

yay fay

does absolutely nothing…
if it doesn’t yay… you know… just saying. it should definitely yay!

88

It’s not in the AUR. I have no plans to add it, since it is mostly experimental. If there is demand, I’ll add it to the AUR, but only if I ever bring it to a state it may be considered complete.

No idea what you’re doing, so difficult to say what part of it is wrong. Are you just trying a script or are you trying to compile the program that generates these scripts?

89

that was my point. a bit around the bush, but… :slight_smile:

90

Just the script above.

91

  1. Clone repo

    git clone git@gitlab.com:Kresimir235/fay-terminal-image-rasteriser.git

  2. Compile program

    cd src
g++ $(Magick++-config --cxxflags --cppflags) -O3 -std=gnu++17 -o fay fay.cpp $(Magick++-config --ldflags --libs)

  3. Place some :frog: image to src directory and run:

    ./fay frog.png
1 Like
92

What does

echo $COLORTERM

return when you run it in Konsole?

93

It’s OK, spotted that it was missing :blush:

94

All I get is

┌05:26:52 WD= [~]
└───freebird@nest ─▶$ git clone git@gitlab.com:Kresimir235/fay-terminal-image-rasteriser.git
Cloning into 'fay-terminal-image-rasteriser'...
git@gitlab.com: Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

which isn’t very helpful. Trying the other command on the source file now (only C experience, none with .cpp)

95

OK - just tried - not even an error message when compiling! (I’m impressed). Seems to work great too :grin:

fay-out1

I know it isn’t a frog - but it might be gazing in admiration at one!

6 Likes
96

Is it wrong I am most happy with freebird@nest? :laughing:

2 Likes
97

Very impressive! but here’s a question: why, out of all the aliases you could have chosen, using string_t = std::string :laughing:

1 Like
98

Thanks!

The choice behind string_t is about as silly as string_t itself, but there is method to my madness. I write code in Kate, and C and C++ highlighting marks all words that end in _t as types, so I just add that to most of the aliases I make.

Screenshot_20210517_090259

I could have used str_t as well.

1 Like
99

Or you could change your editor… :wink:
For example emacs shows those types consistently, even without the _t suffix.

100

I’m happy with Kate. It’s a very good text editor, I like it much more than Emacs. Vim is a close second to Kate, but I like Kate better.

1 Like
101

I can understand that, kate is a very good editor. I could use it too (and I have used it) if I wouldn’t have been friends with emacs for decades…

All editors have their pros and cons. Typically what one chooses to use is what one is familiar with, provided it has enough features and works well.

2 Likes