I know that default "CTRL+B" Windows command works for showing all nested files.
Is there a shortcut to show all nested folders?
I doubt if this feature exists in Total Commander. The built-in tree utility is always good enough for me.
If you don't like console output, just run this inside Total Commander's command line to copy the output to the clipboard:
tree | clip
Of course, you can assign it a shortcut. :)
Total Commander by version differs from the oldest one, if u can't find ur desired shortcut, just simply set this shortcut on the configuration panel as following:
>Start
>Change main menu
>Configuration
>Misc.
>Redefine Hotkeys...
Related
I just started using PyMOL and Unix commands to look at .pdb files and I have a task that I want to perform, but I don't know exactly how to implement it.
You can find the task described below:
"Download this tar file and unpack it using the command line.
This file contains 271 .pdb files and I want to focus in on residues numbered 40-55 in all files using PyMOL from the command line.
Once those residues are focused in PyMOL, I want to save the images and export the snapshots to an html page/format."
I would like to do all this using piping in Unix. I have some of the basics down but I need help with some of the more complex tasks. Any help is greatly appreciated!
Since you want to do this using "piping in Unix", I will describe here the plain command line version on how to proceed. I will deliberately omit the part "export the snapshots to an html page/format" because this goes beyond PyMOL and can be done with many other programs or tools.
First, you want to iterate over the pdb files inside your folder:
for protein in *.pdb;
###launching PyMOL and passing commands here;
done
these commands you are going to need for PyMOL:
First, let's start the PyMOL executable from the shell. Depending on the operating system you work on this may vary. I will use macOS as an example. Further help on how to start PyMOL from the command line you can find here.
/Applications/PyMOL.app/Contents/MacOS/PyMOL -cq $protein -d "###here come the PyMOL commands"
c means, that the PyMOL gui won't start (we don't need it here), and q omits PyMOL's welcome message. $protein is each PDB file we're looping over. d means PyMOL commands are going to be passed.
We are going to use the following commands to get your piece of peptide for each PDB file and create a PNG image:
first we make sure that nothing else will be visible:
hide everything;
now we select your residues 40 through 55 and name this selection "pieceofpeptide":
select pieceofpeptide, resi 40-55;
depending on how you want the representation to look (e.g. cartoon, licorice, lines etc.) you choose the style in the next command:
show cartoon, pieceofpeptide;
Now we make sure that the image is centered (try varying the number, it represents the distance from the object we center):
zoom center, 20;
Finally, let's save this as an image (adjust resolution to your needs):
png $protein.png, width=10cm, dpi=150, ray=1
written as a one-liner the final command eventually looks like this:
for protein in *.pdb; do /Applications/PyMOL.app/Contents/MacOS/PyMOL -cq $protein -d "hide everything;select pieceofpeptide, resi 40-55;show cartoon, pieceofpeptide;zoom center, 20;png $protein.png, width=10cm, dpi=150, ray=1"; done
It is however, much easier to see and edit if you store PyMOL commands in a file like script.pml, or use a Python script, but this is best explained here.
I run simulations for various choices of parameters. For each choice I store the resulting data in a folder, like
/home/me/Documents/MyProject/C=10/1.dat
/home/me/Documents/MyProject/C=10/2.dat
/home/me/Documents/MyProject/C=10/3.dat
...
and
/home/me/Documents/MyProject/C=20/1.dat
/home/me/Documents/MyProject/C=20/2.dat
/home/me/Documents/MyProject/C=20/3.dat
...and so forth.
would like to write a little text file AAA.txt which contains not just the C parameter but all the others too. Then when viewing this folder which contains the data I want to hold my cursor on the little file symbol and have a little box appear. This box should show just the content of AAA.txt, so I can quickly check which set of parameters was used in this particular run.
Anyone know how to do this? I use Ubuntu 14.04
I am not aware of ways to give you a custom "tooltip". As an alternative, you could look into creating custom thumbnails of your .dat files.
See here for how to do that with nautilus; the default file browser for Ubuntu.
Alternatively, you might look into what Gloobus can do for you.
When you scroll up, say to see a log, the first portion of it will not be visible since the terminal only supports a limited no. of lines. So if you want to scroll up and be able to see everything, at least a few pages up, how do you do it?
Use Shift+Page Up and Shift+Page Down.
Piping the output to a pager like the following is a better choice:
command | less
command | more
You can enable unlimited scroll back (or a huge amount if you want).
To do this, go to
File → Profile preferences → Scrolling [tab]
Then, check Unlimited, or set the number of lines desired. And of course, it only applies to the next typed lines.
Some tricks I use-
some terminal applications (gnome-terminal) allow you to increase the scroll-back buffer size
pipe output to a file:
command > file.log
pipe your command to less:
command | less
tail log and pipe to grep to reduce output
tail -f example.log | grep 'search text'
An alternative to screen is using tee to copy all output to a file while still printing it on the terminal:
yourcommand | tee output.txt
Try using the screen command, and set its scrollback buffer to a larger size.
screen has many other benefits and wonderful features.
If all you're doing is looking at a log, you could alternately use a pager such as less
If you want to scroll line by line, you can use
Control+Shift+Up/Down Arrows.
If you are using gnome-term (the default), then you can change your settings. Either set the no. of lines to unlimited, or to a much larger buffer size than the default.
Essentially seconding to #zerick's solution but if you're on gnome-terminal you can modify its config. See this.
If you are in tmux (can create multiple terminal sessions in a single terminal session, highly recommended), you can easily use your normal navigation keys to scroll around after you do Ctrl-b then [, for more details let's take a look at: How do I scroll in tmux?
None of these answer the original question. All answers are how to make new terminal windows (or current one) start behaving a certain way. The question is about how to see whats already scrolled away.
To answer this, each terminal session should have it's own "history" file (not to be confused with what command history is) containing all the stuff that relates to stdin/stdout displayed. I could be wrong but this may be different depending on the terminal emulator you use. Some just trash it when you close the window/ end the session.
I am trying to get this figured out myself so here is the more direct answer in a different thread.
https://unix.stackexchange.com/questions/145050/what-exactly-is-scrollback-and-scrollback-buffer
From what this tells me, I suspect best advice you can get is, for whatever terminal emulator you use, look for where it stores the scrollback buffer and that might be your only hope. It's what I am going to try right now. (and that is IF the session is currently still open, not closed terminal windows)
After creating the devpath in MKS, developers will check in the code to MKS. I want to find the list of files got checked in to the MKS after creation of devpath (from the beginning to the end).
Please help me.
Thanks
You can use the command line interface "rlog" command to see all changes on a devpath.
The basic syntax would be something like: si rlog --devpath=Version2
You can also use the other parameters of the rlog command to limit the output to a date range or other criteria.
Hope this helps.
If you use the GUI you can go to the "project history view", and mark two of the checkpoint bubbles (holding CTRL) and then select "view differences" from the context menu. In that view you can see all the files that were checked in between the selected checkpoints.
So I was hoping that some old school Vim'ers could help me out. These are all separate questions and normally I would put them up each on their own but I'm not sure if that qualifies as question whoring here.
Plus I think if you know enough to be asking any of these questions they will all be coming up in the near future:
I have a library I'm writing and a series of applications that use that library. There doesn't seem to be an easy way(from what I can tell) to build a ctags file for the library and build one for each of my applications and make sure one references the other when I'm in vim.
Using gf to open files from command mode is awesome, but a lot of my include files
don't contain the full path. They refer to an include directory I set in the IDE. How can I set this directory as another point for Vim to start looking for files?
Is there a way to compile a file inside Vim and send the output to a buffer? I'm currently using MSVS 2k3 but I'll be porting over to Linux in a few weeks so if this is possible on either system I'd appreciate it.
Re 3)
If you put a makefile in your root dir, you can simply write
:make
This will run make and (iirc) put any errors into a seperate buffer, and make vim goto the first compile error. From there you can navigate all erroring lines using :next-error
Also, see this page
http://wiki.beyondunreal.com/Legacy:Vim
and
http://linux.byexamples.com/archives/287/perform-grep-and-make-in-vim/
for details on how to show the result in a seperate console.
1- tags files are independent, and can be used together. See :h 'tags'
I can't tell what is the easy way to build tags files. I have one that consists in using two plugins of mine:
one (draft) plugin that knows how to update C++ tags files (it should be easy to adapt it to other filetypes),
and another (local_vimrc) that helps me define directories-local .vimrc. Thus for any files within a given directory hierarchy, I can adapt the &tags options to use the relevant tag files, and the current tag file that will be rebuilt automatically (or when a keybinding is triggered). (Plugins like project should do the trick as well)
2- :h 'path'
3- :h :make
HTH.
2)
:cd {path}
For help:
:he cd
A few others like :lcd might be better suited. Just scroll down that help page.
This is rather off topic, but might still be useful: if you're using Visual Studio a lot and like Vim, you might want to look at ViEmu. It's the best Vim-emulation for any IDE I've yet seen, and the cost is really low. :) And no, I'm not getting a commission. :P
It's not obvious, but if you open a directory instead of a file, it's nicely browseable.
e.g.
:e . (colon-e-dot)
:e .. (colon-e-dot-dot)
will let you browse from your current directory or its parent.
(understanding that you were probably hoping for a capability to have vim accept e.g.
:e abc.txt
and have it look in several directories, which I don't know how to do.)