Working with Linux

Recommendations

Info

Here we see the files that are in our trash. It is only showing the files that were put there with thetrash command. We can see the date when they were deleted, the hour, and the exact location. If we'dhave had multiple files with the same name and path, they would have been listed here, and we couldhave identified them by the deletion date.In order to restore a file from trash we will use the command:restore-trash
It will show us a list of options and ask for a number corresponding to the file we want restored. Inthis case we will select 1, meaning we want to restore the json file.We open the file and we can see that the content was not altered in the process.In order to remove all the files in the trash, we use:trash-empty
Page 2 and 3:
Working with Linux - Quick Hacks fo
Page 4 and 5:
Network - Who's listening?Autoenv -
Page 6 and 7:
Working with Linux - Quick Hacks fo
Page 8 and 9:
Melwyn DsaCover WorkMelwyn Dsa
Page 10 and 11:
www.PacktPub.com
Page 12 and 13:
Why subscribe?Fully searchable acro
Page 14 and 15:
PrefaceOur mission is to save Linux
Page 16 and 17:
What you need for this bookIdeally,
Page 18 and 19:
ConventionsIn this book, you will f
Page 20 and 21:
Customer supportNow that you are th
Page 22 and 23:
PiracyPiracy of copyrighted materia
Page 24 and 25:
Chapter 1. IntroductionThis book is
Page 27 and 28:
Terminator - the ultimate terminalT
Page 29 and 30:
Preferences menuIt's an customizing
Page 31 and 32:
And voila! This is our newly config
Page 33 and 34:
Ctrl + Shift + E for a vertical spl
Page 35 and 36:
Text zoom: Ctrl + + and Ctrl + -
Page 37 and 38:
Guake - not Quake!Terminator works
Page 39 and 40:
I believe you can guess what this d
Page 41 and 42:
We can use Guake in full screen by
Page 43 and 44:
The tool is automatically added to
Page 45 and 46:
For example, we might want to updat
Page 47 and 48:
With ClipIt, you can copy and paste
Page 49 and 50:
Vim is renowned for its exotic keyb
Page 51 and 52:
Press the Insert key again to go to
Page 53 and 54:
productive in the coolest terminal
Page 55 and 56:
instructions for installing the oh-
Page 57 and 58:
Let's create a file, say readme.md.
Page 59 and 60:
You can now see the branch name in
Page 61 and 62:
History navigation: Click on arrow
Page 63 and 64:
To see a list of shortcuts, run the
Page 65 and 66:
joe is the string we are searching
Page 67 and 68:
If we don't know exactly what chara
Page 69 and 70:
To find all the lines that have onl
Page 71 and 72:
This will replace every occurrence
Page 73 and 74:
Pipes and subshells - your shell's
Page 75 and 76:
"df -h": This shows the disk usage
Page 77 and 78:
ps aux: This prints all processes w
Page 79 and 80:
cat lorem.txt| tr " " "\n": Transfo
Page 81 and 82:
imagination and how well you learn
Page 83 and 84:
As you can see, the value test is p
Page 85 and 86:
In our case, we will be selecting f
Page 87 and 88:
esacdoneecho "invalid option"exit 1
Page 89 and 90:
./script.sh --ip wlp3s0We can see t
Page 91 and 92:
This way we can start the script, w
Page 93 and 94:
Shell scripting librariesTo really
Page 95 and 96:
of the current working directory (o
Page 97 and 98:
case ${CMD} inpublicip)print_public
Page 99 and 100:
Supercharging VimLet's start by ope
Page 101 and 102:
Let's choose desert!
Page 103 and 104:
We can do the same thing for xml fi
Page 105 and 106:
Keyboard kung fuNow that we have Vi
Page 107 and 108:
Other handy shortcuts are:G: Go to
Page 109:
:1,$s/CWD/DIR/g:1,$ - start from li
Page 112 and 113:
This will delete everything from li
Page 114:
cat lorem.txt | tr " " "\n" | grep
Page 117 and 118:
When Vim splits the screen, it open
Page 119 and 120:
Plugin steroids for VimIn this sect
Page 121 and 122:
As we can see, before installing sn
Page 123 and 124:
Here we can see all the snippets av
Page 125 and 126:
A page describing the different enc
Page 127 and 128:
It also has the benefit that it's s
Page 129 and 130:
Using heredocs is a common techniqu
Page 131 and 132: Sed - one-liner productivity treasu
Page 133 and 134: If we check the content of the file
Page 135 and 136: As you can see, the text was update
Page 137 and 138: You can run, but you can't hide…
Page 139 and 140: You see here that both readme.md an
Page 141 and 142: You can see here all files that don
Page 143 and 144: Find can also locate files based on
Page 145 and 146: A good folder to search is ~/.local
Page 147 and 148: As we can see, electron has a few e
Page 149 and 150: In order to do this, we combine fin
Page 151 and 152: tmux - virtual consoles, background
Page 153 and 154: For demonstration purposes, we will
Page 155 and 156: This will kill the running session.
Page 157 and 158: You also have the possibility to cr
Page 159 and 160: Ctrl + b &: delete
Page 161 and 162: Network - Who's listening?When work
Page 163 and 164: Other useful information we get fro
Page 165 and 166: You can quickly understand the form
Page 167 and 168: As you can see, there is again the
Page 169 and 170: non-standard. To actually connect t
Page 171 and 172: hostnames and ports. For a deeper u
Page 173 and 174: Now let's do the same thing for pro
Page 175 and 176: autoenv: Are you sure you want to a
Page 177 and 178: export environment=devexport versio
Page 179 and 180: Autoenv can really come in handy, a
Page 181: Let's assume we don't need the file
Page 185 and 186: Chapter 5. Developers' TreasureIn t
Page 187 and 188: Clicking on the button generates a
Page 189 and 190: You can find the files used in this
Page 191 and 192: The first and most important part o
Page 193 and 194: The format of the output image will
Page 195 and 196: This will create a JPEG image with
Page 197 and 198: Let's try to shrink the large PNG i
Page 200 and 201: Alright, now let's try and do the s
Page 202 and 203: Go with the Git flowGit is by far t
Page 204 and 205: We can see that we are now on the d
Page 206 and 207: This command will tell us that we h
Page 208 and 209: This switches us over to our releas
Page 210 and 211: We see that the only two available
Page 212 and 213: GitFlow also comes with an enhanced
Page 214 and 215: Analyzing the git hooks directory,
Page 216 and 217: Merging Git conflicts with easeNow
Page 218 and 219: After this, we can run the followin
Page 220: Now we can easily see the two files
Page 223 and 224: In general, most modern IDEs offer
Page 225 and 226: Now do a rehash and type the follow
Page 227 and 228: Click on the link provided by ngrok
Page 229 and 230: JSON jamming in the new ageNowadays
Page 231 and 232: If we want to grab the request meth
Page 233 and 234:
If we want to use the output as inp
Page 235 and 236:
Say, for example, if we want to cal
Page 237 and 238:
Since that the syntax for accessing
Page 239 and 240:
To skip printing empty bodies, we c
Page 241 and 242:
We can even perform arithmetic oper
Page 243 and 244:
There we can see an example of cons
Page 245 and 246:
This will send gedit to the backgro
Page 247 and 248:
Now we see that the mouse pointer h
Page 249 and 250:
Chapter 6. Terminal ArtAll work and
Page 251 and 252:
To make this recurrent, we can incl
Page 253:
Now, with our newly learned skills,
Page 256 and 257:
Let your friends be amazed by the c
Page 258 and 259:
IndexAautoenvabout / Autoenv - Set
Page 260 and 261:
Ddesert / Color scheme desertdigabo
Page 262 and 263:
Ffind commandusing / You can run, b
Page 264 and 265:
Iidentify / Shrinking spells and ot
Page 266 and 267:
LlinuxURL, for developers / Are you
Page 268 and 269:
NNERDtreeabout / Plugin steroids fo
Page 270 and 271:
PpathogenURL / Plugin steroids for
Page 272 and 273:
Ssedone-liner productivity / Sed -
Page 274 and 275:
VVimsupercharging / Supercharging V
show all

Working with Linux

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?