1
In eshell, you can redirect stdout to an emacs buffer in a few different ways.
rails g scaffold --help > (switch-to-buffer “*scaffold*“)
rails g scaffold --help >>> #
The only known way to run eshell script from shell (outside emacs). This starts emacs UI. Add --batch to run without UI.
emacs --debug-init -q --eval “(progn (require 'em-script) (let ((eshell-rc-script \“/tmp/wtf.esh\“)) (eshell)))“
Use shebang + exec emacs --script to run emacs code as a shell script but also as emacs code, for example load-file
#! /bin/sh
“:“; exec emacs --no-site-file --script “$0“ -- “$@“ # -*-emacs-lisp-*-
(print (+ 2 2))
Eshell accepts ksh-like syntax. Amog others you can specify a group of files by (file1|file2|...|fileN). But, that is a bit tricky since parentheses also indicate lisp forms to be evaluated (for an example see the answer by lawlist). Use '' to tell it is a predicate, not form: cp /Users/HOME/.0.data/.0.emacs/.0.sources/emacs/(buffer.c|buffer.h|dispextern.h|keyboard.c|nsterm.m|w32term.c|window.h|xdisp.c|xterm.c)'' ~/Desktop/emacs/src/
In cron, use
```
0 * * * * bash -l -c 'sh /my/script.sh'
```
The -l makes bash act as login shell - that is, read the owner's ~/.bash_profile (which generally reads .profile)
Command can be used to set desired_count, max_count, etc, on a service. Something like: aws ecs --cluster=goosepilot list-services; aws ecs --cluster=goosepilot update-service --service=“arn:aws:ecs:us-east-2:823978586159:service/goosepilot/goosepilot“ --desired-count=0
Funding the whack Jimmy Dore ... Like his pals Elon Musk and Peter Thiel, Sacks is using his wealth and online clout to unite conservatives and former leftists in a reactionary movement against liberalism.
Go to your DNS provider's website, log in to your account, and locate the DNS management settings for your domain.
Configure a CNAME to point to the AWS validation server. For example, if the validation server is _cjhwou20vhu2exampleuw20vuyb2ovb9.j9s73ucn9vy.acm-validations.aws, enter _cjhwou20vhu2exampleuw20vuyb2ovb9.j9s73ucn9vy.acm-validations.aws. Amplify uses this information to verify ownership of your domain and generate an SSL/TLS certificate for your domain. Once Amplify validates ownership of your domain, all traffic will be served using HTTPS/2.