Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4611516
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T01:16:42+00:00 2026-05-22T01:16:42+00:00

On running: vim /tmp/blah :q echo $? I get an exit status of 1

  • 0

On running:

vim /tmp/blah
:q
echo $?

I get an exit status of 1. This is breaking various things including Git. If I run vim without my vimrc:

vim -u NONE /tmp/blah
:q
echo $?

I get an exit status of 0. I use Pathogen so this also effectively disables plugins. Does anyone have a suggestion for efficiently determining the cause of the exit status? I’m aware of running Vim verbosely and logging to a file. Should I be looking for something specific in this file?

If there is a method of finding the exact line that determines the exit status I would love to know of it as searching around didn’t turn much up.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T01:16:43+00:00Added an answer on May 22, 2026 at 1:16 am

    Finally found this command in help: :cq[uit]. So after you do verbose logging, search for \<cq\%[uit]\>.

    Update: There are also methods to alter the exit status using vim compiled with some interpreters support: at least, the following works:

    python import sys
    python sys.exit(1)
    " (same for python3)
    
    perl exit 1
    

    I do not know other languages enough to write here examples of code that would quit vim with different exit status. Note also that such commands inside files sourced using :pyfile, :rubyfile and other :*file should also work, as well as this code in a modules not distributed with plugin.

    I think the most efficient way here at this point is disabling plugins until you find the source of the problem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Running FxCop on my code, I get this warning: Microsoft.Maintainability : 'FooBar.ctor is coupled
this is what my git status ' result looks like: # On branch master
I run vim in a full-screen bash terminal with transparency enabled. (This is a
I open several files in Vim by, for example, running vim a/*.php which opens
When running a vim instance in gnu screen hitting shift enter in insert mode
running git instaweb in my repository opens a page that says 403 Forbidden -
Running into a problem where on certain servers we get an error that the
Running OS X Leopard an MacBook Pro from Jan. 2008. I used to run
Running a ServiceHost with a single contract is working fine like this: servicehost =
Running ipconfig /all shows a Teredo Tunneling Pseudo-Interface. What is that? Does this have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.