Post your handy self made command line utilities

parchd · 2014-10-21 12:31:57

I haven't tried it yet, I'm supposed to be working too and the pdfs I had problems with are already converted.

skanky · 2014-10-21 12:35:06

parchd wrote:

I haven't tried it yet, I'm supposed to be working too and the pdfs I had problems with are already converted.

Okay, my thinking is that you'll still need the intermediate step as sed will try each command on every line - though address patterns may help. I think there's a command to skip to the next line, but can't remember it. So I can possibly think of 2 or 3 ways to get round it, but as I say I don't have time. I'll have a crack later, if I get a chance - it's been a while since I needed to do any sed, and I need a refresher.

fsckd · 2014-10-21 13:32:09

skanky wrote:

EDIT: sorry, I think I made a big mistake and rather than confuse people, it's better to delete what I wrote.

Now I have no idea what you guys are talking about.

skanky · 2014-10-21 13:57:12

fsckd wrote:

skanky wrote:
EDIT: sorry, I think I made a big mistake and rather than confuse people, it's better to delete what I wrote.
Now I have no idea what you guys are talking about.

Sorry, I did try to go back and undo that but had lost it - I was too busy really to try an answer, but quickly fired one off, then thought better of it, then changed my mind and the whole thing was a mess.

I thought the sed line could be shortened to:

sed -i 's/0 0 0 sc/1 1 1sc/g; s/1 1 1 sc/0 0 0 sc/g' /tmp/pdfinvtmp

But see my above post for why I think that won't work.

skanky · 2014-10-21 16:57:25

@parchd - right, I've had a chance to look at this properly. Sorry about the earlier debacle.

To summarise:

* You can amalgamate all the sed commands into one set of '...' (script).
* You can embed un-escaped new lines into the script, or use ;'s
* You are able to remove the intermediate step (see below)
* In GNU sed you can edit the tmp file in place

Here's the sed line taking all into account, and tested on a *very* simple test file:

sed 's/0 0 0 sc/1 1 1 sc/g;t; s/1 1 1 sc/0 0 0 sc/g' /tmp/pdfinvtmp

Note the "t" in there. That says that if the current line has been substituted, branch to the label, and if there is no label, to the end of the script.
Thus if we make a substitution on the current line we don't then substitute it back on the next command. If both settings are on the same line, it will fail to do the second substitution. I don't have pdftk installed so haven't checked. If that is the case, you could use one command to do both at the same time.

Again, sorry for the noise.

andya · 2014-10-30 13:00:49

I wrote this bash / zsh script for mass file numbering:

#!/bin/sh
#########
##
##  Script for: Mass numbering of files
##
##  It SHOULD prevent files from being destroyed. Try at your own risk.
##  Use -t flag to just echo.
##  Use -b d to print dir name
##
#########

usage () {
          printf "     Usage:\n"
          printf "              \e[1;36mnumb -b photo *.*\e[0m\n"
          printf "                         ... will number all files in current dir Pics as photo_001, photo_002, preserving extensions\n"
          printf "              \e[1;36mnumb -c 12 -p 2 *.*\e[0m\n"    
          printf "                         ... will number all files in current dir Pics as Pics_12, Pics_13, preserving extensions\n"
	  }

PAD=3
COUNTER=1
RANGE=1

BASE=

while getopts "c::p::b::r::tsm" OPTIONS; do
    case "${OPTIONS}" in
        c)
            COUNTER=${OPTARG}
            ;;
        p)
            PAD=${OPTARG}
            ;;
        b)
	    if [ ${OPTARG} = d ]; then
		BASE=${PWD##*/}
	    else
	        BASE=${OPTARG}
            fi
	    ;;        
        r)  
            RANGE=${OPTARG}
            ;;
        t)  
            TRY=y
            ;;
	s)
	    SWITCH=y
	    ;;
	m)
	    MANTAIN=y
	    ;;
    esac
done
shift $((OPTIND-1))

if [ "$#" -lt 2 ]; then
   usage
   exit 1
fi

IFS=$'\n\t'
	
for OLDNAME in "$@"; do

    if [ -n "$SWITCH" ]; then
        NEWBASE=$(printf "%0${PAD}d_${BASE}" ${COUNTER})
    elif [ -z "$SWITCH" ]; then
	NEWBASE=$(printf "${BASE}_%0${PAD}d" ${COUNTER})
    fi

    if [ "$BASE" = "" ]; then
	NEWBASE=$(printf "%0${PAD}d" ${COUNTER})
    fi
	
    if [ -n "$MANTAIN" ]; then
        NEWNAME=${NEWBASE}_${OLDNAME}
    else
	NEWNAME=${NEWBASE}.${OLDNAME#*.}
    fi
	
    if [ -n "$TRY" ]; then
        echo "mv --backup=nil ${OLDNAME} ${NEWNAME}"
    else
        mv --backup=nil ${OLDNAME} ${NEWNAME}
    fi
    
    let COUNTER=COUNTER+${RANGE}
done

######
## TODO: 
##       !!!!  let it be recursive:
#              MAXDIRDEPTH=1
#              PAD=3
#           for PATHSUBDIR in $(find -maxdepth ${MAXDIRDEPTH} -type d \( ! -name '.*' \)); do
#               i=1;
#              for PATHFILE in $(find "${PATHSUBDIR}" -maxdepth 1 -type f -name '*.*' | sort); do
#              NEWBASE=$(printf "$(basename ${PATHFILE%/*})_%0${PAD}d" $i);
#                echo "mv --backup=nil ${PATHFILE} ${PATHFILE%/*}/${NEWBASE}.${PATHFILE#$PATHSUBDIR/*.}";
#              let i=i+1;
#              done;
#            done
##
##
##        !!!!  exit 1 when arguments are missing, etc
##        !!!!  update usage
######

Edit: removed bashisms (thanks @jasonwryan)
Edit 2: added options

Last edited by andya (2014-11-01 13:00:37)

jasonwryan · 2014-10-30 16:19:20

You have a POSIX shebang, but are using bashisms (`echo -e`, `[[` and `$(..)`)...

steve___ · 2014-10-30 16:41:31

Hey Jason, is "$(..)" not POSIX compliant?

jasonwryan · 2014-10-30 16:43:07

steve___ wrote:

Hey Jason, is "$(..)" not POSIX compliant?

It is. My bad for posting this early...

Xaero252 · 2014-11-05 02:16:48

Here's a quick watchdog script I made to emulate the functionality of the "Borderless Gaming" app on Windows. Just add it to your session and create a ~/.fullscreen.lst file with the titles of games you wish to be borderless fullscreen'd; one per line:

#!/bin/bash
#"Borderless Fullscreen" automatic toggling script
#By Xaero252 @ OCN (overclock.net)
#Distributed with the "don't be a douche" license
#Just don't try and claim you thought this up or whatever

#First, let's start a container loop with a sleep command to keep it from eating CPU.
while true; do 
	sleep 1 #We'll use 1 second, we don't want users to wait forever.
	while read title; do
		if ! xprop -name "$title" 2>/dev/null | grep -q _NET_WM_STATE_FULLSCREEN; then
			wmctrl -r "$title" -b toggle,fullscreen
		fi
	done < ~/.fullscreen.lst #This way it's per-user.
done

The game must be run in Windowed mode for this to function as intended, but it fills the gap for a lot of games that don't have this functionality on Linux by default. (Stepmania, Minecraft, etc.)

rwd · Today 21:06:36

I tend to have a bunch of 'screen' sessions running on a headless system. When I want to resume the 3rd session this alias let's me do that with minimal typing:

scr 2

Without arguments it just lists active sessions.

function scr(){
    if [[ $# == 0  ]]
    then
        screen -list
    else
        var_screen_num="${1}"
        arr_screen_id=($(screen -list | grep -Pzo  '(\d+\.[a-z0-9-]+\.\S+)'))
        screen -r "${arr_screen_id[$var_screen_num]}"
    fi
}

Last edited by rwd (Today 21:07:56)

Arch Linux

#2476 2014-10-21 12:31:57

Re: Post your handy self made command line utilities

#2477 2014-10-21 12:35:06

Re: Post your handy self made command line utilities

#2478 2014-10-21 13:32:09

Re: Post your handy self made command line utilities

#2479 2014-10-21 13:57:12

Re: Post your handy self made command line utilities

#2480 2014-10-21 16:57:25

Re: Post your handy self made command line utilities

#2481 2014-10-30 13:00:49

Re: Post your handy self made command line utilities

#2482 2014-10-30 16:19:20

Re: Post your handy self made command line utilities

#2483 2014-10-30 16:41:31

Re: Post your handy self made command line utilities

#2484 2014-10-30 16:43:07

Re: Post your handy self made command line utilities

#2485 2014-11-05 02:16:48

Re: Post your handy self made command line utilities

#2486 Today 21:06:36

Re: Post your handy self made command line utilities

Board footer