Vim in cloud, part 1
But why? Let me share my experience with using vim in the cloud, specifically on Google Cloud Platform (GCP) and GitHub’s Codespaces. There is plenty of places where you can learn vi/vim basics, all its modes which confuses beginners – I’m assuming you’ve already figured it out. For many years I’ve been using vim as
gdb – looking at core dump
So an application gave up the ghost and you finde a “corpse”. At least you can learn a signal it caught – see Program terminated with signal 11, Segmentation fault. $ gdb core.614.1636347290GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7Copyright (C) 2013 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.htmlThis is
seeking (linux) messages (log)
So they (a vendor) wants you to look if an application failure has a system cause? You reported an issues on 01-11-2021 06:00. You are intersted on what happened around 6:00 A.M. that day. Raffly # cd /var/log # head messages #what’s the oldest Oct 31 03:06:01 apz-sagb1p rsyslogd: [origin software=”rsyslogd” swVersion=”8.24.0-57.el7_9.1″ x-pid=”1697″ x-info=”http://www.rsyslog.com”] rsyslogd
sed for csv debug
Instead of fancy and sophisticated thoughts lets share a daily experience 😉 You’ve collected data.csv: field1,filed2,filed3 A,B,C D,E,F f,a,i,l H,I,J L,M,N and while importing to a DB (sqlite in this example) you’ve got: sqlite> .mode csvsqlite> .import data.csv datadata.csv:4: expected 3 columns but found 4 – extras ignored Now, how to find faulty records (while
Archives
Calendar
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||