Vim ignores statusline setting in vimrc [Solved]

Dear Archers,
I'm trying to modify my vim statusline. At this stage, my goal is to get vim to recognise any kind of statusline modification made in the vimrc, because at the moment no such modification appears to be recognised whatsoever.
I tried both a sample vimrc from the wiki and a blank vimrc containing nothing but the line,
set statusline=%t
For both vimrcs, the statusline setting was ignored. When I'm in vim, I can manually run the command,
:set statusline=%t
and the effect is apparent and immediate. All my other vimrc settings appear to be parsed in the correct manner; only this one specific setting seems to be ignored (but without warnings/errors).
I also did general googling on such topics as
Me Googling wrote:"vimrc" "ignores" "statusline"
and found this Stack Overflow thread which suggests using ruler instead of statusline, but still I couldn't get it to work.
If anyone can point out what I'm doing wrong, I would really appreciate it.
Last edited by /dev/zero (2012-05-31 22:15:49)

JackH79 wrote:
Strange. Is vim at least using any other modifications in your vimrc?
If no, then I'd say that maybe it doesn't use the same vimrc you're working with.
If it does, then I'm out of ideas for the moment.
Edit: Maybe check this.
Thanks for your help. I noticed this problem while trying to modify my existing vimrc, which is much larger. That pre-existing vimrc works quite well, with or without these changes to the statusline settings. The changes just get ignored. This leads me to think that $HOME/.vimrc isn't being ignored entirely. For some reason, only the statusline part seems to be ignored.
The output of
:version
within vim appears identical to
vim --version
within bash, and so:
$ vim --version | grep vimrc
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
system gvimrc file: "/etc/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
I could suppose that some error is making vim fall back on /etc/vimrc - but wouldn't this also make an error message appear, and make the colorscheme fall back to default as well? If there's a problem, then shouldn't the commands fail to work when I run them manually, and shouldn't a warning or error be issued?
I could post my normal vimrc, but I think at this stage it would just muddy the waters. I'd like to focus on getting the given minimal vimrc to work first. After that, I will see whether the solution works in a more realistic vimrc.

Similar Messages

Vim ignores ~/.vimrc [solved]

Since update to 7.1.68-1 vim no longer reads my ~/.vimrc. Some commands (i.e. set number) work when entered manually, others do not (syntax on reports "Sorry, the command is not available in this version.")
Any clues to recover line numbers and syntax?
Thanks.
Edit:
Ooops! Solved, it seems that I was executing the classical vi. Before the update vi was the same as vim, now it seems they're different binaries and although :help in vi reports "Vim version 7.1", it behaves as vi.
These lines in ~/.bashrc resume previous behaviour:
export EDITOR=vim
export VISUAL=vim
alias vi=vim
Last edited by atordo (2007-08-14 01:22:07)

JackH79 wrote:
Strange. Is vim at least using any other modifications in your vimrc?
If no, then I'd say that maybe it doesn't use the same vimrc you're working with.
If it does, then I'm out of ideas for the moment.
Edit: Maybe check this.
Thanks for your help. I noticed this problem while trying to modify my existing vimrc, which is much larger. That pre-existing vimrc works quite well, with or without these changes to the statusline settings. The changes just get ignored. This leads me to think that $HOME/.vimrc isn't being ignored entirely. For some reason, only the statusline part seems to be ignored.
The output of
:version
within vim appears identical to
vim --version
within bash, and so:
$ vim --version | grep vimrc
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
system gvimrc file: "/etc/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
I could suppose that some error is making vim fall back on /etc/vimrc - but wouldn't this also make an error message appear, and make the colorscheme fall back to default as well? If there's a problem, then shouldn't the commands fail to work when I run them manually, and shouldn't a warning or error be issued?
I could post my normal vimrc, but I think at this stage it would just muddy the waters. I'd like to focus on getting the given minimal vimrc to work first. After that, I will see whether the solution works in a more realistic vimrc.

How to resolve the issue "ignoring compiler setting" in Tomcat Web Server

Hi All,
In the Environment set up
jdk1.3.1_09
Apache Tomcat 4.1.24
I'm getting the following error when i request a jsp file.
Please help to solve this issue.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.
[javac] C:\Program Files\Apache Group\Tomcat 4.1\work\Standalone\localhost\_\jsp\ConnectionPooling_jsp.java:44: cannot resolve symbol
[javac] symbol : class PCSTDatabaseConnectionPoolingBean
[javac] location: class org.apache.jsp.ConnectionPooling_jsp
[javac] PCSTDatabaseConnectionPoolingBean connectionpool = null;
[javac] ^
[javac] C:\Program Files\Apache Group\Tomcat 4.1\work\Standalone\localhost\_\jsp\ConnectionPooling_jsp.java:46: cannot resolve symbol
[javac] symbol : class PCSTDatabaseConnectionPoolingBean
[javac] location: class org.apache.jsp.ConnectionPooling_jsp
[javac] connectionpool = (PCSTDatabaseConnectionPoolingBean) pageContext.getAttribute("connectionpool", PageContext.SESSION_SCOPE);
[javac] ^
[javac] C:\Program Files\Apache Group\Tomcat 4.1\work\Standalone\localhost\_\jsp\ConnectionPooling_jsp.java:49: cannot resolve symbol
[javac] symbol : class PCSTDatabaseConnectionPoolingBean
[javac] location: class org.apache.jsp.ConnectionPooling_jsp
[javac] connectionpool = (PCSTDatabaseConnectionPoolingBean) java.beans.Beans.instantiate(this.getClass().getClassLoader(), "PCSTDatabaseConnectionPoolingBean");
[javac] ^
[javac] 3 errors
     at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
     at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
     at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
     at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
     at java.lang.Thread.run(Thread.java:479)

[javac] PCSTDatabaseConnectionPoolingBean connectionpool = null;
[javac] ^
[javac] C:\Program Files\Apache Group\Tomcat 4.1\work\Standalone\localhost\_\jsp\ConnectionPooling_jsp.java:46: cannot resolve symbol
The compiler doesn't know what PCSTDatabaseConnectionPoolingBean is. Have you properly imported the class?

Second disk (HDD) spins down occasionally, ignoring energy setting.

I've UNCHECKED the setting "Put the hard disk(s) to sleep when possible" because I find no value in this. Yet my second disk (HDD) occasionally spins down when the computer is left idle for a while. (My first disk is an SSD). It's all apple-made, no custom or user changes inside. It's not a big deal, but I know spinning down and up again adds wear to the disk and it's something I'd rather not have the disk doing. It's ignoring the setting, why is this? and can I do something about it?

I was affraid that would be the case, blah! Well it's an HDD so I can hear it click when it spins down and back up. It's mostly just happening when the computer is idle for a long time but it's still a wasteful act because it usually spins right back up again after a while and it SEEMS this time around it won't wait equally long before it spins down again but does so relatively quickly again as if the drive figured something minor just happened and that it can just go "back to sleep" when it's done, which on it's turn adds to the wear if I'd leave it like this for hours on since SOME activity is always present from time to time on any disk.

[Solved] Vim ignoring modelines

This line is at the end of a load of my bash scripts, but none of the settings are getting applied (for the several files I've tried).
It's the last line in my file.
# vim:set ts=4 sw=4 ft=sh et:
I've got no modeline setting in my vimrc, so no idea why it's being ignored unless there's one. I've read though the vim help and have done a quick internet search, but can't find anything obvious.
Any ideas?
Last edited by skanky (2012-07-11 09:32:43)

JackH79 wrote:
I think the expandoption shouldn't have a colon. What happens if you try:
# vim: ts=4 sw=4 ft=sh et
That doesn't change behaviour, and I think it goes against what the help says.
However, it looks like the issue is elsewhere, as looking at the settings, the modeline isn't getting ignored, it's the behaviour isn't as I expect from those settings. This could be user error, but whatever it is, it isn't modelines getting ignored. So I'll mark this as solved and look into the behaviour issue.
Many thanks for your replies.

Ignore Tab-Setting in a JTextPane

Hello,
i have a JTextPane and I need a Tab Size 0. I want to ignore the Tab-Setting, cuz I got an XML-Editor, with automaticaly indent.
Does anyone Have an Idea ?

This thread might help:
http://forum.java.sun.com/thread.jsp?forum=57&thread=331679

Distiller arbitrarily ignores compatibility setting

Here's the scenario: Two people sitting next to each other with the exact same setups (WinXP, Adobe TCS with FrameMaker 8 and Acrobat 3D).
Person A (me) makes a PDF from FrameMaker using the established standards (including to set compatibility with Acrobat 5.x/PDF 1.4). Everything works just fine.
Person B, who is using a fresh install of Windows and TCS, makes a PDF from the same FrameMaker files, using the same settings (same .joboptions), and everything APPEARS to be the same. However, the in-house print shop (which uses something called "Preps 5.2") cannot print from Person B's PDF. The job fails and gives no error messages.
Examination of the PDF properties shows that Person B's PDF is compatible with Acrobat 7.x/PDF 1.6. Huh? So I sit with Person B and watch her make a PDF. She chooses the correct job options, makes the PDF, and bingo, same problem; it ups the compatibility to 7.x/1.6 in the final result.
Aside from any silly reasons why the print shop apparently can't handle Acrobat 7.x/PDF 1.6, why is her Distiller ignoring her PDF settings?
More importantly, how can we fix this?
Thanks!
e
d

Hmmm. It turns out to be pilot error of some sort on the part of Person B. I sent her my .joboptions file, which she used instead of the one she created according to the same criteria, and now it works OK.

Messed up the pacman DB with wrong date set in bios [solved]

Solved by reinstallation and some searching around for a few hours.
Last edited by MoonSwan (2008-07-27 02:05:20)

WonderWoofy wrote:I think you may find relevant information here. I ahve seem many of these threads in the forums lately. Are you dual booting w/ another operating system... in particular, one that uses localtime for the hardware clock (and there is only one that does this).
Thanks I'll look at that entry. Still I'd like to point out that this page clearly says that the timezone is to be set in rc.conf, which is a bit confusing. I must've followed this guide to get to my current configuration. I am dual booting with multiple other systems (xubuntu, win7, puppy, crunchbang) so from what I've read win7 might be the problem, but I haven't started it since i installed arch and my time has been off from the start.
Should I simply use NTP now that pacman is working again?
Thanks
Last edited by miek (2012-09-03 17:41:56)

Apache ignoring HTTP_HOST set through PlsqlCGIEnvironmentList?

Hi,
I just want to see if anyone else has had a problem with Apache ignoring the HTTP_HOST value set through PlsqlCGIEnvironmentList in the wdbsvr.app DAD?
I've set it like this:
PlsqlCGIEnvironmentList HTTP_HOST=hostname:8050
in wdbsvr.app in the Apache/modplsql/cfg directory. We're using the Apache that comes with the EBusiness suite. I've stopped and restarted the server, even going so far as to stop the entire app and bounce the database to see if it would make this thing stick. For some reason it's still showing up as hostname:8250 in the flash chart xml.
Is there anything else I can do? Just for debugging, here is the entire DAD from wdbsvr.app:
[DAD_apex]
connect_string = db_name
password = password
username = apex_public_user
default_page = apex
document_table = wwv_flow_file_objects$
document_path = docs
document_proc = wwv_flow_file_mgr.process_download
reuse = Yes
enablesso = No
stateful = STATELESS_RESET
nls_lang = American_America.AL32UTF8
PlsqlCGIEnvironmentList HTTP_HOST=hostname:8050
Thanks! I think this just needs another set of eyes...
Mark

Hi Jason,
Thanks for the document link! Unfortunately that didn't work either. My DAD now has cgi_env_list=HTTP_HOST=servername:8050, but it's still pulling in as servername:8250. I set it, bounced the Apache server and did a select owa_util.get_cgi_env('HTTP_HOST') from dual through SQL workshop and it still came back with the wrong port number.
Do you think I should clear the cache while the Apache server is down?
Thanks,
Mark

Setting up abs [SOLVED]

I am attempting to follow the setup procedure for ABS from the wiki but have stumbled at pretty much the first step.
I used pacman to get abs and adjusted /etc/abs/abs.conf to
# /etc/abs/abs.conf
# the top-level directory of all your PKGBUILDs
[ "$ABSROOT" = "" ] && ABSROOT="/var/abs/"
# Supfiles to be parsed by abs (in this order)
# (prefix a module with a ! to disable it)
SUPFILES=(core extra !unstable community !testing)
but when I run
#abs
the system sits for a while before returning
==> Updating core...
Cannot connect to 1.0.0.0: Connection timed out
==> ERROR: An unknown error has occured. Exiting...
I have searched the forums for the error message and google but cannot see what is wrong.
I read through the wiki page and tried reinstalling wget and cvsup but still got the same error.
Can someone please point me in the right direction
Thanks
Last edited by alfie (2008-03-11 22:41:35)

Thanks for all your help, I have this solved now.
Just for info the problem was that the router has a buggy implementation of DNS in that if you use it for local network DNS then for certain applications (e.g. wget and apparently csup) it will insist on trying to resolve all addresses without using the external DNS that has been set.
This apparently only affects Linux, it works in Windows (see [url=http://www.dslreports.com/forum/remark,12484917]link[url])
The resolution - of sorts, was to add
66.211.213.17 cvs.archlinux.org
to my /etc/hosts file which enables it to be resolved correctly.
To help anyone searching the router is a DLink DSL-G604T although this bug also affects the G504T model
Interestingly, if I take the firewall off completely I have no access at all outside my local network but I think this is another topic more suited to a DLink forum.
Thanks again for all your help, you got me thinking in the right direction
edit: corrected code line
Last edited by alfie (2008-03-11 22:41:17)

Belle: File dates ignore time setting (uses GMT)

I've come to discover that the device uses GMT in relation to file creation / modification dates and ignores the time zone setting. I was kept unaware of this by being able to use Nokia Multimedia Transfer to import camera files to iPhoto. Having to connect USB in Mass Storage mode reveals this limitation. However I am not at all sure if this was the case prior to Belle, though I assume so.
Seems like a oversight in the core of the OS, but if not please fix this. The time zone setting should be more than cosmetic. File dates should not be disregarded on a device that can handle as many files and file types as modern smartphones (N8-00 here) can. It *is* important.
Also, update all your software for Macintosh while you're at it, please.
TIA!

Thanks for the answer, I read everything except the man page for mktime :-(
Well I can't remember where I read that about "gmtime" but you are right:
I will use gmtime instead of mktime and it works, it converts it to a GMT time.
Thanks again for your precious help.
Cheers,
Gilles

Z87-G45. VCore setting ignored. Set to 1.147V but maxes out at 1.3V!!

Hi guys, first post here and I couldn't find any similar threads. I'm a complete noob with overclocking, but I had a 4.1GHz overclock on my i5-4670K with 1.147V (1.195V w/ -0.049 offset, adaptive mode) stable for over a year. All other settings were at default.
I reinstalled windows 3 weeks ago, updated the BIOS from 1.8 to 1.9 and the ME drivers. I didn't touch the overclock settings afterwards due to studies, but when I did try a few days ago, the vcore setting I enter in the BIOS seems to be ignored. Using the same settings as before the reinstall (1.195vcore, -0.049 offset, adaptive mode), it is reported by CPU-Z to be 1.28-1.3V during a Prime95 stresstest.
Unlikely factors:
-error in CPU-Z voltage reading = not likely as the temps are about 20 degrees celsius higher than they previously were (70+ previous, 95-99 current)
-prime95 = i used this same program to stresstest the CPU before the reinstall without similar issues
What I've tried so far:
- Changing CPU multiplier to 41x vcore to 1.147 without offset = 1.33V reported by CPU-Z (Picture shows these settings)
- Tried rolling back the BIOS version to 1.8 using MFlash = no change
The attached picture shows the settings, but the CPU meter temps are still 80+ as I only ran the test for 5 seconds for fear of overheating.
I hope there's a solution to this. I don't have much understanding of what controls vcore (bios, OS, ME, etc) so I don't know what else I can do to diagnose and fix this. If anyone could offer any solutions or help, I would appreciate it greatly.
Thanks for your time!
EDIT: I only used Command centre to show the voltage setting in the screenshot. BIOS was used to change settings. I might add that command centre has always crashed within half an hour of opening it, and thus I've never relied on it.

Hi again, just an update on my situation. I've effectively corrected my problem, but my OC settings are still not functioning exactly like before.
I reinstalled windows (not a system image restore) without installing any of the mobo drivers that liveupdate recommends. I can achieve a stable 4.1GHz OC with 1.168V (reported by CPU-Z). The only error is that my vcore is set to 1.195 (offset -0.049), which used to give a VID of 1.147V, not 1.168V.
Still, I'm quite happy that at least I can run a stable 4.1GHz overclock at below 1.2V, which didn't work when I started this thread.
Now the only question left, since I purposely didnt install most mobo drivers, is whether I need to install the Chipset drivers or "management engine" drivers listed on my motherboard's support page? (http://www.msi.com/support/mb/Z87-G45-GAMING.html#down-driver&Win7 64)

InDesign ignoring hyphenation setting

Hello Everyone,
I included the user dictionary into my InDesign document. And I set the settings to break the hyphenation only after 3 letters, but InDesign is breaking the words even after 1 letter as per my user dictionary. Could you please advise whether InDesign will not consider my own settings for user dictionary terms?
Thanks,
Praveen

When you add new words you should do it
to the dictionary of the correct language
insert breaking points where hyphenation should be done.
E.g. if I want to insert a new German word, I have to select the correct German Dictionary, that is "Deutsch Rechtschreibrefor 2006" (German Reform 2006), then I enter the Word like "Donaudampfschifffahrtsgesellschafftskapitänsausbildungsinstitutsdirektorssekretärinsschr eibmaschine". Ok the word would be a little bit too long and would not work with automatic hyphenation. So I enter tildes (~~) as breaking points. 2 of them as average hyphenation, 1 on primary and 3 on places of possible but not prefered hyphenations. So it would look like this:
"Do~~~ nau~~ dampf~~~ schiff~~~ fahrts~~ ge~~~ sell~~~ schaffts~ka~~~pi~~~täns~aus~~~bil~~~dungs~~insti~~~tuts~di~~~rek~~~tors~sek~~~re~~~tä~~~r ins~schreib~~ma~~~schi~~~ne"

Can't set default browser [SOLVED]

Hi, I'm running GNOME-Shell (I wasn't sure if this belongs to testing forum or not), and I want Opera to be my default browser.
As for DE, I changed gconf-editor>desktop>gnome>url-handlers>http and https to "opera %s". Nothing happened.
As for Arch itself, i added "opera" here: https://wiki.archlinux.org/index.php/Ch … lt_browser
Nothing happened, my default is still Firefox. Any other solution?
Last edited by centos (2011-04-19 14:10:17)

Well yes, but I wasn't sure if this was gnome-related
Thanks, this works. But I'd have sworn that I checked this menu before and Opera wasn't one of the choices.
Solved.

The date and time setting go crazy[SOLVED]

Hello,
Each time, I boot up the time setting changes. Sometime two hours behind, sometimes five. Even if I set the time and date by using the "date -s" command or kde time setting feature when reboot the time changes.
Any idea how to fix this for good?
Thanks,
jmak
Last edited by jmak (2009-11-20 00:19:17)

Thanks for all the suggestions.
This what happened. From some strange reasons the system clock setting and the distro setting were different. The bios clock was two hours before the distro clock. I adjusted the bios clock to real time—to correct time thinking this will set the disto time to the correct time too. Rebooted and I was put on the commandline with an error message:"superblock last mount time Thu Nov 19 11:41:29 2009, now=Thu Nov 19 10::53:27 2009 is in the future"
Then I entered the root password and did a "fsck" and rebooted. It booted up fine
but the distro time setting was still wrong. Rebooted again and checked the bios clock and it was reset to the distro clock. Both were wrong but at least have the same settings. Then I boot up again and set the time to the right setting in KDE. Rebooted and checked the bios clock which was adjusted to the distro setting—in other words to the correct settings. Now the time is ok. So it seems that the bios setting depends on the distro setting. I thought it was the other way around.
My computer is relatively new, 2 years old, so I dont think this was a battery problem. Also, I have other distros installed and I haven't experienced these kinds of problems with those distros.
Lately, I experimented with a few distros on different partitions, and what I am suspecting is that those might reset the bios clock which caused the inconsistencies in Kde.
jmak

Vim ignores statusline setting in vimrc [Solved]

Similar Messages

Maybe you are looking for