I added the following .vimrc file to the home directory of Vim for iOS on my iPad.
set showcmd
set number
set guifont=Courier:h24
imap jk <Esc>
For some mysterious reason, all commands work fine except set number. Since manually typing :set number still works, it can't be that Vim for iOS doesn't support displaying line numbers. I have no clue why it behaves differently when I put it in .vimrc. Any ideas?
Check with
:verbose set number?
where this got set last.
If that doesn't provide a hint, capture a log with vim -V20vimlog and check for :set number commands. (This assumes that you can launch Vim on the command-line on the iPad. If not, add :set verbose=20 verbosefile=vimlog to your ~/.vimrc.)
Also, the :scriptnames command shows all scripts that ran after your ~/.vimrc.
Related
I have started to use Powerline for my terminal prompt and while I have gotten it all working I am not sure how to configure the segments. I have tried messing around with the files in the ~/.local/lib/python3.8/site-packages/powerline directory but nothing seems to be changing. I specifically want to remove the exit code extension so any help on that would be great.
Yes I have tried reading the docs but I couldn't understand what file to edit and where and what to change.
(I want to remove the red 1 segment shown here)
I have now discovered my issue. In order to reload the config you need to put the following in the terminal. I also moved my config files to ~/.config/powerline
powerline-daemon --replace
tqdm prints an empty bar after loop ends. I tried implementing this solution, but with no success.
The problem does not exist if I remove the print statement (see code).
My code is:
for PhotoIdx in tqdm(range(Nphotos), position=0, leave=True):
....
end
print("something")
return x
I attach a photo with what is outputted to the terminal (the third bar is from another python file).
This appears to be a Pycharm issue, which can be fixed by editing the Run/Debug Configuration in Pycharm and checking the box that says "Emulate terminal in output console"
The standard output terminal appears to have trouble with properly outputting text applications that use certain terminal features, although I don't know the exact cause of this particular problem.
it seems to be a bug from Pycharm.
It's working fine inside the terminal.
Have a good day
The employees of our company use gnome-terminal run from Debian workstations to access a variety of systems running different O/Ss on our local network. Everything works very well except that the host systems and their applications use different character sets, either ISO-8859-1 ("Latin 1") or UTF-8, and the server applications notably do NOT adapt to the locale of the user. This requires the user to manually set gnome-terminal's character set encoding each time one starts a new session!
(In case that's not clear, we always want to log into system X using ISO-8859-1, and always log into system Y using UTF-8. This has to do with the relative antiquity of the O/S of each system, the older ones having little or no accomodation of UTF-8 while the newer ones deal rather grumpily with ISO-8859-1.)
It seems to me that gnome-terminal's character set encoding should be associated with the system one's logging into instead of the system one's calling from. And that therefore, the character set should be one of the parameters that can be pre-set in the profile. This is the way other terminal emulators behave, notably the Windows and Mac emulators that we use outside the office.
But in lieu of configuring it in the profile (which is not possible), does anyone know a way of setting the character set encoding as part of a command line invocation of gnome-terminal?
I've been trying to solve this annoyance off-and-on for years... any solution would receive our eternal gratitude. :)
in the good old times, gnome-terminal support --disable-factory, you can set up for local editing files:
#!/bin/sh
export GDM_LANG="de_DE#euro"
export LANG="de_DE#euro"
export RC_LANG="de_DE#euro"
export LC_ALL="de_DE#euro"
gnome-terminal --disable-factory
or remote access to a linux-box:
#!/bin/sh
export GDM_LANG="de_DE#euro"
export LANG="de_DE#euro"
export RC_LANG="de_DE#euro"
export LC_ALL="de_DE#euro"
gnome-terminal --disable-factory --tab --title="Server1 DE" --command "ssh user#Server1"
Now at gnome 3.10 I get
... Option "--disable-factory" is no longer supported ...
So, I am with you and will keep looking ...
Mario
This worked for me.
LANG=en_US.iso885915 /usr/bin/gnome-terminal
I switched from netbeans to emacs and I am pretty happy with the change. The thing I am missing the most is autocompletion and jump to definitions. In order to get this I have installed Rsense. It works fine for the gems code, though, I cannot jump-to-definitions of my Rails project nor autocomplete according to the methods I defined.
I tried to add my project's load path to Rsense's load_path configuration, though, it still doesn't work.
Does anyone know how to get this working?
You can use tags for browsing through files and jumping directly to function definitions.
I use Exuberant Ctags (its got Ruby support). You can download it from here.
I am assuming that you are working on windows. Getting the tags to work initially on windows is a pain especially if you are using emacs for the first time.
These are the steps I followed:
Install Cygwin from here.
Include the cygwin\bin\ folder in your environment variable PATH. E.g. here
Install exhuberant ctags. Note that emacs may sometime have a built in ctags. Later on you will have to use the ctags command in cygwin to create tags. At that time you may encounter some errors in case it uses the ctags in emacs instead of exuberant ctag.
Once you have installed ctags, add that to the environmental variable PATH as well.
If you have a small project with relatively lesser number of files (<500). So you just need a single global TAGS file. For that open cygwin, change your directory to the root directory of your project and type in the command ctags -R -e Check this out for other approaches
Your tags file will be created. It will be named "TAGS" and will be present in the root directory of your project.
Next open emacs, and browse through the code. In case you come across a function and want to jump to its definition, put your cursor on the function name and press M-. your minibuffer should then show something like Find tag (default <function-name>): Press Enter and voila!!! you are magically transported to the function definition!!!
Note: You may have to specify the TAGS file the first time you use the M-. This needs to be done only once after emacs startup. You can also modify your .emacs file to take in the TAGS file automatically on startup.
Refer to this and this for more info for tags related commands in emacs.
Until now, I have been using rtags to jump to definitions. It's not perfect, but it does the trick in many cases.
I get the following when I start my Zsh.
Usage: prompt <options>
Options:
-c Show currently selected theme and parameters
-l List currently available prompt themes
-p [<themes>] Preview given themes (defaults to all)
-h [<theme>] Display help (for given theme)
-s <theme> Set and save theme
<theme> Switch to new theme immediately (changes not saved)
It seems to be set by some theme file, since the same text is here.
How can you disable the notification in Zsh?
This isn't a startup message. It's the error/default help message displayed when the prompt command is used without arguments or erroneous arguments. Find out where you're using it, and fix/delete it.
You'll want to search through the files that zsh loads on startup, here is a list from their documentation
Look for a misconfigured prompt command line and try commenting it out or better fixing it.