Skip to content
This repository has been archived by the owner on Feb 19, 2023. It is now read-only.
/ slacker Public archive

A CLI Slack tool using SHELLSCRIPT.(Just to send messages)

License

Notifications You must be signed in to change notification settings

Cj-bc/slacker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

日本語版はこちら : https://github.com/Cj-bc/slacker/blob/master/README_JP.md

slacker

CLI Slack tool.(Just to send messages) Lang: shellscript(bash) slacker allows you to send messeges without being away from terminal.
slacker just send messages.Not get any messages.

feature

  • you're now free from your mouse and trackpad to use slack app!
  • Notifications? Please get them from your slack app ;)
  • Now, it supports pipe command (Add:2017/11/11)
  • Developing environment is macOS Sierra10.13.2(2018/01/14)

infomations of making

I'll write blog about making slacker on http://blog.y-modify.org

  • English
  • Japanese
    will be supported

Needed permitions

  • channels:read
  • channels:write
  • im:write
  • users:read
  • users:write
  • team:read

Needed commands

  • python -mjson.tool
  • awk(not gnu-awk) And...

LICENSE

This software is released under MIT License,see LICENSE

in_prgress

  • slacker.sh
  • texts/Error_Codes.sh

ToDos

  • make the core part
  • automatically get a token -> someday
  • Deside Error codes
  • Use camelcase/snakecase
  • Need to know how to output errormessage directly to basic output(= commandline)
  • open slack app when slacker is called with -o option or sonething like that.
  • Japanese support
  • Make man page
  • cope with homebrew
  • Check whether token is avilable
  • Don't require initializing when it is upgraded
  • better user experiences ( guide for use )
  • treat with heredocument
  • shortcut for person/room's name(make alias)
  • send space-letter( )
  • Check whether channel/user exist when we set them
  • the way to see config
  • enable to send message without selecting channel
  • multi workspaces

problems I have

  • What's the best grammer ??
     slacker set <arg> <values>
     slacker -c <channel>
     slacker <messages>
  • how about alias ??
  • which is better to change user(or channel) selection or not when sendfunc.send() is called with arguments.

Questions

  • Can i write ${$1:1} ? -- on sendfunc.send()
  • Can i nest ``