Shell - Revision history

Elvince: add category

2017-05-15T14:45:25Z

add category

Elvince: terminal here

2017-04-15T11:01:52Z

terminal here

Elvince: /* More colors */

2016-09-19T12:22:41Z

More colors

Elvince: replace ncurses soft with built-in

2016-09-19T12:21:21Z

replace ncurses soft with built-in

Elvince: /* Search the bash, zsh or fish history with Ivy-mode */

2016-08-22T20:31:04Z

Search the bash, zsh or fish history with Ivy-mode

Elvince: search shell history with ivy-mode

2016-07-23T11:35:03Z

search shell history with ivy-mode

Elvince: /* Customisation */ history delete dups

2016-05-05T08:46:14Z

Customisation: history delete dups

Elvince: git pcomplete

2016-02-13T02:11:37Z

git pcomplete

FredN: Add syntax highlighting for code

2016-01-01T21:15:54Z

Add syntax highlighting for code

FredN: Add syntax highlighting for code

2016-01-01T21:13:46Z

Add syntax highlighting for code

← Older revision		Revision as of 14:45, 15 May 2017
Line 222:		Line 222:
	[[Category:Shell]]		[[Category:Shell]]
	[[Category:Intermediate]]		[[Category:Intermediate]]
		+	[[Category:Programming]]
		+	[[Category:Programming_languages]]

← Older revision		Revision as of 11:01, 15 April 2017
Line 202:		Line 202:

	Use [https://github.com/ieure/shell-here shell-here] to open an Emacs shell in the current directory.		Use [https://github.com/ieure/shell-here shell-here] to open an Emacs shell in the current directory.
		+
		+	== Terminal here - open an external terminal ==
		+
		+	[https://github.com/davidshepherd7/terminal-here terminal-here] is meant to open an external terminal in the directory associated with the current buffer.

	== dirswitch ==		== dirswitch ==

@@ Line 24: / Line 24: @@
 = Customisation =
-== More colors ==
+== Fix, add colors and highlight text ==
 If you have bad colors in the output, try using '''ansi-mode''':

← Older revision		Revision as of 12:21, 19 September 2016
Line 1:		Line 1:
−	'''Shell-mode''' gives access to a shell in a normal emacs buffer, meaning you can move around and edit it as usual. A drawback is that you can not launch programs like htop or other ncurses ones, like you would in term-mode.	+	'''Shell-mode''' gives access to a shell in a normal emacs buffer, meaning you can move around and edit it as usual. A drawback is that you can not launch programs like htop or other ncurses ones, like you would in term-mode (however, there are often built-in alternatives).

	= Usage =		= Usage =

@@ Line 99: / Line 99: @@
 == Search the bash, zsh or fish history with Ivy-mode ==
-Again a code snippet from [http://blog.binchen.org/posts/use-ivy-mode-to-search-bash-history.html Redguardto's blog]. You can find adaptation for zsh in the comments and [https://gist.github.com/heikkil/177ff4c4b8a02d574958 for fish].
+Again a code snippet from [http://blog.binchen.org/posts/use-ivy-mode-to-search-bash-history.html Redguardto's blog]. This snippet defines a function "counsel-yank-bash-history" that one call manually. We are presented an interactive minibuffer (with ivy, à la ido) with all the history. The line we select is put in the kill ring, ready to be pasted.
 <source lang="lisp">
@@ Line 118: / Line 120: @@
          (kill-new val)
          (message "%s => kill-ring" val))))
 </source>

← Older revision		Revision as of 11:35, 23 July 2016
Line 96:		Line 96:

	Note that if you want to persist more variables (mini-buffer history,…), enable '''savehist-mode''' and configure the variables you wish to persist between sessions. See {{Command\|customize-group RET savehist RET}}.		Note that if you want to persist more variables (mini-buffer history,…), enable '''savehist-mode''' and configure the variables you wish to persist between sessions. See {{Command\|customize-group RET savehist RET}}.
		+
		+	== Search the bash, zsh or fish history with Ivy-mode ==
		+
		+	Again a code snippet from [http://blog.binchen.org/posts/use-ivy-mode-to-search-bash-history.html Redguardto's blog]. You can find adaptation for zsh in the comments and [https://gist.github.com/heikkil/177ff4c4b8a02d574958 for fish].
		+
		+	<source lang="lisp">
		+	(defun counsel-yank-bash-history ()
		+	"Yank the bash history"
		+	(interactive)
		+	(let (hist-cmd collection val)
		+	(shell-command "history -r") ; reload history
		+	(setq collection
		+	(nreverse
		+	(split-string (with-temp-buffer (insert-file-contents (file-truename "~/.bash_history"))
		+	(buffer-string))
		+	"\n"
		+	t)))
		+	(when (and collection (> (length collection) 0)
		+	(setq val (if (= 1 (length collection)) (car collection)
		+	(ivy-read (format "Bash history:") collection))))
		+	(kill-new val)
		+	(message "%s => kill-ring" val))))
		+	</source>

	== Sync environment variables like $PATH from the shell ==		== Sync environment variables like $PATH from the shell ==

← Older revision		Revision as of 08:46, 5 May 2016
Line 131:		Line 131:

	See [https://github.com/leoliu/pcmpl-git-el pcmpl-git] and you'll be able to complete git commands in the emacs shell.		See [https://github.com/leoliu/pcmpl-git-el pcmpl-git] and you'll be able to complete git commands in the emacs shell.
		+
		+	== Other settings ==
		+
		+	=== Remove duplicates from history ===
		+
		+	(setq history-delete-duplicates t)
		+
		+	This will affect all histories, not only shell.

	= See also =		= See also =

← Older revision		Revision as of 02:11, 13 February 2016
Line 127:		Line 127:

	This is possible with [https://github.com/mbriggs/emacs-pager emacs-pager]. Now things like ''less'' will open in a new buffer with colorized output.		This is possible with [https://github.com/mbriggs/emacs-pager emacs-pager]. Now things like ''less'' will open in a new buffer with colorized output.
		+
		+	== Complete git commands and options with pcomplete ==
		+
		+	See [https://github.com/leoliu/pcmpl-git-el pcmpl-git] and you'll be able to complete git commands in the emacs shell.

	= See also =		= See also =

@@ Line 63: / Line 63: @@
 So you are in shell-mode and you are annoyed that emacs opens a new window with the list of completions when you press TAB and you like the pop-up menu that zsh offers ? The solution is to ask [http://company-mode.github.io/ company-mode] to do the shell completion. It has a built-in backend ''company-capf'' which fetches completion candidates from emacs' ''completion-at-point-functions'' (the same mechanism that powers completion in the shell) as such completion offered by company is as accurate as the built-in shell-mode while making the user interface very convenient. We can activate it with:
-    (add-hook 'shell-mode-hook #'company-mode)
+<source lang="lisp">
-    (define-key shell-mode-map (kbd "TAB") #'company-manual-begin))
+(add-hook 'shell-mode-hook #'company-mode)
 (define-key shell-mode-map (kbd "TAB") #'company-manual-begin))
 And the result:
@@ Line 88: / Line 89: @@
 <source lang="lisp">
-    (add-hook 'shell-mode-hook 'my-shell-mode-hook)
+(add-hook 'shell-mode-hook 'my-shell-mode-hook)
-    (defun my-shell-mode-hook ()
+(defun my-shell-mode-hook ()
-      (setq comint-input-ring-file-name "~/.zsh_history")  ;; or bash_history
+  (setq comint-input-ring-file-name "~/.zsh_history")  ;; or bash_history
-      (comint-read-input-ring t))
+  (comint-read-input-ring t))
 </source>
@@ Line 113: / Line 114: @@
 If you want it to be more interactive, you can set:
-    (setq fasd-enable-initial-prompt nil)  ;; don't ask for first query but fire fuzzy completion straight away.
+<source lang="lisp">
 === Get ido completion to cd in shell ===

@@ Line 53: / Line 53: @@
 Every line representing a path to a file will be colorized and made clickable, so that you can jump to that file and that line, like in compilation-mode (specially useful when compiling a program or running tests):
-    (add-hook 'shell-mode-hook 'compilation-shell-minor-mode)
+<source lang="lisp">
 Now you can use key bindings from the mode: use {{CommandKeys|C-x `|next-error}} (backquote) to go to the next error detected in the shell. You can't do that in an xterm !