similar to: [LLVMdev] Vim auto completion

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Vim auto completion"

2010 Oct 30
0
[LLVMdev] Vim auto completion
The clang patches are now applied, so vim auto completion now works mostly out-of-the-box -- just build clang, set up your PATH for clang and clang++, and copy utils/vim/vimrc to ~/.vimrc (or symlink, or do your own thing). To configure the clang command-line, look for the g: configuration variables in the vimrc file. I'm open to suggestions about the handling of function parameters. One
2010 Oct 21
0
[LLVMdev] Vim auto completion
On Oct 21, 2010, at 2:11 PM, Tobias Grosser wrote: > Hi, > > I have been watching the vim/clang autocompletion in utils/vim/vimrc for a while. What is the status of this work? The last information I got is, that there where still some patches missing, but this was before the clang-2.8. > Any updates? Is it supposed to work with clang-2.8? It requires a clang patch, which I
2013 Feb 28
2
[LLVMdev] Propose to use rest.vim for vimrc of LLVM
Hello list, I use LLVM's vimrc and found that this setting below is useful when editing of reStructuredText file. llvm/utils/vim/vimrc " Enable syntax highlighting for reStructuredText files. To use, copy " rest.vim (http://www.vim.org/scripts/script.php?script_id=973) " to ~/.vim/syntax . augroup filetype au! BufRead,BufNewFile *.rst set filetype=rest augroup END
2007 Jun 28
3
Vim differences between C4 and C5
I have installed CentOS 4.5 and 5 on 2 separate machines, and both have default installs of vim-enhanced on each of them. I noticed that I can get syntax highlighting as a regular user, sudo and as root in C4.5. In C5 I only get highlighting as a regular user. I diff'ed my /etc/vimrc files between each install there is no changes and neither root ~ has a .vimrc file. I had put "# vim:
2016 Oct 29
2
Stupid vim question
On 10/29/2016 02:49 PM, Frank Cox wrote: > On Sat, 29 Oct 2016 14:39:03 -0700 > Alice Wonder wrote: > >> How do I get it to stop doing that? > > http://superuser.com/questions/278442/how-to-make-vim-not-fold-everything-automatically > Thank you, it appears the folding is the term I should have used in my search. Putting set foldlevelstart=1 in the ~/.vimrc didn't
2013 Feb 28
0
[LLVMdev] Propose to use rest.vim for vimrc of LLVM
Thanks, Journeyer. I applied the patch with r176235. In future, you can submit patches to the llvm-commits mailing list. :) -bw On Feb 27, 2013, at 9:03 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello list, > > I use LLVM's vimrc and found that this setting below is useful when > editing of reStructuredText file. > > > llvm/utils/vim/vimrc
2007 Dec 07
10
Where are my VIM colors?
Maybe, it's stupid question but I've just installed CentOS5 and when I'm going to edit some of my conf files I see no colors as it did in old CentOS4x... I'm using: [root at domian:~]$ echo $TERM xterm Thanks in advance, Regards, Israel
2016 Oct 29
1
Stupid vim question
On 10/29/2016 04:32 PM, Alice Wonder wrote: > On 10/29/2016 03:06 PM, Alice Wonder wrote: >> On 10/29/2016 02:49 PM, Frank Cox wrote: >>> On Sat, 29 Oct 2016 14:39:03 -0700 >>> Alice Wonder wrote: >>> >>>> How do I get it to stop doing that? >>> >>>
2003 Feb 12
2
rl_callback_read_char error on Solaris 7
This question is about compiling R-1.6.2 from source on a Sparcstation-20 machine running Solaris 7, gcc-2.95.3 and readline-4.2 (both gcc and readline from sunfreeware.com). I searched the r-help archive and the FAQ. The errors seem to be related to the binary readline libraries, and I have /usr/local/lib/libreadline.a,libreadline.so@, and libreadline.so.4. The attached errors are from
2016 Oct 29
3
Stupid vim question
on very large files, vim will condense display - e.g. +-- 8 lines: static inline void php_openssl_rand_add_timeval() -------------------------------------------------------------------------------------------------------------------------------------------------- #endif +-- 29 lines: static int php_openssl_load_rand_file(const char * file, int *egdsocket, int *seeded)
2013 May 16
3
vim-puppet syntax highlight
Hi I am trying to install vim-puppet for syntax highlight of puppet manifest file. I first installed vim-puppet and then vim. Then I ran "vim-addon-manager -w install puppet" I am still unable to see the colours on site.pp bala@WheezyMaster:~$ vim-addon-manager # Name User Status System Status editexisting removed removed justify
2002 Oct 07
1
[LLVMdev] VIM syntax highlighting
I have made a vim syntax highlighting script for LLVM. It can be found at llvm/utils/vim/llvm.vim. You should copy this file to your ~/.vim/syntax/ directory and add the following lines to your .vimrc file to have it automatically load on a .ll file. augroup filetype au! BufRead,BufNewFile *.ll set filetype=llvm augroup END Misha claims to be making a script for all you emacs
2011 Nov 12
3
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
Hi Dave, Thanks for the results. What platform is this on? And do these failures occur with 2.9? -bw On Nov 10, 2011, at 9:51 AM, David A. Greene wrote: > greened at obbligato.org (David A. Greene) writes: > >> Nikola Smiljanic <popizdeh at gmail.com> writes: >> >>> I'm not sure if this makes a difference but I ran this >>> >>> make -j
2011 Nov 15
0
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
Bill Wendling <wendling at apple.com> writes: > Hi Dave, > > Thanks for the results. What platform is this on? And do these failures occur with 2.9? Platform is Debian Linux testing, x86_64. clang is a disaster with 2.9 unfortunately, so I can't test it: /bin/cp Output/sse.expandfft.llvm.o.compile.time Output/sse.expandfft.simple.compile.time
2011 Aug 25
4
[LLVMdev] Changes to Debian's linker object files breaks building LLVM [crti.o, crt1.o, crtn.o]
I've got a simple workaround which obviously everyone will figure out: mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crti.o crti.o mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crt1.o crt1.o mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crtn.o crtn.o My real question concerns whether or not I should file a bug report against Debian not having a
2010 Feb 26
2
[LLVMdev] VIM mode line comments
Is it kosher to include vim mode line comments inside of LLVM source files? I would like to do this inside of the MicroBlaze backend to ensure that tabs are expanded into exactly two spaces. I see that right now the following files have these vim mode line comments: include/llvm/ADT/SetVector.h lib/Archive/ArchiveInternals.h lib/Linker/LinkModules.cpp lib/Transforms/IPO/DeadTypeElimination.cpp
2009 Nov 03
1
Run R code by Vim-R-plugin (How do I to run two or more programs at the same time)?
Dear list, I use R on Ubuntu 9.04 by Vim editor with vim-R-plugin. I want to use Vim to run two R programs A.R and B.R. At beginning, I sent A.R to R prompt by pressing "\rf" and "F5" on my keyboard, and it works well. Meanwhile, I want to sent another file B.R to another R window. When I press "\rf", the R window shows up and still runs A.R. How could I run B.R in
2011 Nov 15
2
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
On Nov 15, 2011, at 9:41 AM, David A. Greene wrote: > Bill Wendling <wendling at apple.com> writes: > >> Hi Dave, >> >> Thanks for the results. What platform is this on? And do these failures occur with 2.9? > > Platform is Debian Linux testing, x86_64. > > clang is a disaster with 2.9 unfortunately, so I can't test it: > > /bin/cp
2009 Jan 08
3
How to select a block in gnome-terminal or in vim
Hi, When I connect to a Cisco router and issue the show ip interface command, the output is similar as follows: Interface IP-Address OK? Method Status Protocol Ethernet0/0 192.168.12.1 YES NVRAM up up Serial0/0 unassigned YES NVRAM administratively down down Ethernet0/1 unassigned YES NVRAM administratively down
2020 May 14
2
ld.lld ignoring --sysroot
Hello, I'm trying to compile a Linux hello world executable on macOS. The first step is simple: clang -c -target x86_64-linux-gnu -c -o hello.o hello.c But linking results in an error: ld.lld --sysroot=/linuxroot/ -o hello -m elf_x86_64 \ -dynamic-linker /lib64/ld-linux-x86-64.so.2 \ /lib/crt1.o \ /usr/lib/x86_64-linux-gnu/crti.o ../hello.o \ /usr/lib/x86_64-linux-gnu/libc.so \