123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165 |
- ;;; multishell-autoloads.el --- automatically extracted autoloads
- ;;
- ;;; Code:
- (add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
- ;;;### (autoloads nil "multishell" "multishell.el" (24066 55384 139305
- ;;;;;; 633000))
- ;;; Generated autoloads from multishell.el
- (autoload 'multishell-pop-to-shell "multishell" "\
- Easily navigate to and within multiple shell buffers, local and remote.
- Use a single `universal-argument' (\\[universal-argument]) to launch and choose between
- nalternate shell buffers, and a doubled universal argument to also set your
- choice as the ongoing default. Append a path to a new shell name to launch
- a shell in that directory, and use Emacs tramp syntax to launch a remote
- shell. There is a shortcut to manage your list of current and
- historical shells, collectively, using `multishell-list' - see below.
- Customize-group `multishell' to set up a key binding and tweak behaviors.
- Manage your collection of current and historical shells by
- recursively invoking \\[multishell-pop-to-shell] at the
- `multishell-pop-to-shell' universal argument prompts, eg:
- \\[universal-argument] \\[multishell-pop-to-shell] \\[multishell-pop-to-shell]
- \(That will be just a few keys if you do the above
- customization.) Hit ? in the listing buffer for editing commands.
- ==== Basic operation:
- - If the current buffer is shell-mode (or shell-mode derived)
- buffer then focus is moved to the process input point.
- (You can use a universal argument go to a different shell
- buffer when already in a buffer that has a process - see
- below.)
- - If not in a shell buffer (or with universal argument), go to a
- window that is already showing the (a) shell buffer, if any.
- In this case, the cursor is left in its prior position in the
- shell buffer. Repeating the command will then go to the
- process input point, per the first item in this list.
- We respect `pop-up-windows', so you can adjust it to set the
- other-buffer/same-buffer behavior.
- - Otherwise, start a new shell buffer, using the current
- directory as the working directory.
- If a buffer with the resulting name exists and its shell process
- was disconnected or otherwise stopped, it's resumed.
- ===== Universal arg to start and select between named shell buffers:
- You can name alternate shell buffers to create or return to, by
- prefixing your \\[multishell-pop-to-shell] invocation with single or double
- `universal-argument', \\[universal-argument]:
- - With a single universal argument, prompt for the buffer name
- to use (without the asterisks that shell mode will put around
- the name), defaulting to 'shell'.
- Completion is available.
- This combination makes it easy to start and switch across
- multiple shell restarts.
- - A double universal argument will prompt for the name *and* set
- the default to that name, so the target shell becomes the
- primary.
- See `multishell-primary-name' for info about preserving the
- setting across emacs restarts.
- - Manage your collection of current and historical shells by
- recursively invoking \\[multishell-pop-to-shell] at either of the
- `multishell-pop-to-shell' universal argument prompts, or at any
- time via \\[multishell-list]. Hit ? in the listing buffer for
- editing commands.
- ===== Select starting directory and remote host:
- The shell buffer name you give to the prompt for a universal arg
- can include an appended path. That will be used for the startup
- directory. You can use tramp remote syntax to specify a remote
- shell. If there is an element after a final '/', that's used for
- the buffer name. Otherwise, the host, domain, or path is used.
- For example:
- root shell starting in /etc.
- The buffer will be named \"*example.net*\".
- starting in /var/log on example.net named \"*#ex*\".
- via gateway.corp.com to your homedir on interior.corp.com. The
- buffer will be named \"*interior*\". You could append a sudo
- hop to the path, combining the previous example, and so on.
- File visits from the shell, and many common emacs activities like
- dired, will be on the host where the shell is running, in the
- auspices of the target account, and relative to the current
- directory.
- You can change the startup path for a shell buffer by editing it
- at the completion prompt. The new path will not take effect for
- an already-running shell.
- To remove a shell buffer's history entry, kill the buffer and
- affirm removal of the entry when prompted.
- ===== Activate savehist to retain shell buffer names and paths across Emacs restarts:
- To have emacs maintain your history of shell buffer names and paths,
- customize the savehist group to activate savehist.
- \(fn &optional ARG NAME HERE)" t nil)
- ;;;***
- ;;;### (autoloads nil "multishell-list" "multishell-list.el" (24066
- ;;;;;; 55384 119305 513000))
- ;;; Generated autoloads from multishell-list.el
- (autoload 'multishell-list "multishell-list" "\
- Edit your current and historic list of shell buffers.
- If optional COMPLETING is nil, we present the full
- `multishell-history' list in a popped buffer named '*Shells*'.
- In the buffer, hit ? or h for a list of commands.
- When optional COMPLETING is non-nil, it must be a list of
- multishell-history completion candidate entries, as provided by
- `completing-read'. Then we present the list as a part of
- minibuffer completion.
- You can get to the shells listing by recursively invoking
- \\[multishell-pop-to-shell] at the `multishell-pop-to-shell'
- `universal-argument' prompts.
- \(fn &optional COMPLETING)" t nil)
- ;;;***
- ;;;### (autoloads nil nil ("multishell-pkg.el") (24066 55384 658069
- ;;;;;; 744000))
- ;;;***
- ;; Local Variables:
- ;; version-control: never
- ;; no-byte-compile: t
- ;; no-update-autoloads: t
- ;; End:
- ;;; multishell-autoloads.el ends here
|