Can't force close buffer

[alexanderkyte]

If I've got multiple buffers open, the second that I open an org file I lose the ability to :q! out of all of my
buffers. I'm simply told

"No write since last change."

And it switches to the next buffer. :q!-ing this one, moves back to the org buffer. This continues ad infinitum.

In the case that I don't want to save progress, this requires making a new terminal session and sending a sigterm to vim.

[hsitz]

Alexander --

I can't reproduce this behavior. q! works fine for me, in non-org buffer
and in org buffer, regardless of whether edits have been made. Can you
give me a more detailed set of steps to reproduce?

-- Herb

On Wed, Oct 22, 2014 at 7:09 AM, Alexander Kyte [email protected]
wrote:

If I've got multiple buffers open, the second that I open an org file I
lose the ability to :q! out of all of my
buffers. I'm simply told

"No write since last change."

And it switches to the next buffer. :q!-ing this one, moves back to the
org buffer. This continues ad infinitum.

In the case that I don't want to save progress, this requires making a new
terminal session and sending a sigterm to vim.

—
Reply to this email directly or view it on GitHub
#75.

[hsitz]

Also, could you check whether the :qall! command works for you in situation
where you're getting this error? -- Herb

On Wed, Oct 22, 2014 at 7:52 AM, Herbert Sitz [email protected] wrote:

Alexander --

I can't reproduce this behavior. q! works fine for me, in non-org buffer
and in org buffer, regardless of whether edits have been made. Can you
give me a more detailed set of steps to reproduce?

-- Herb

On Wed, Oct 22, 2014 at 7:09 AM, Alexander Kyte [email protected]
wrote:

If I've got multiple buffers open, the second that I open an org file I
lose the ability to :q! out of all of my
buffers. I'm simply told

"No write since last change."

And it switches to the next buffer. :q!-ing this one, moves back to the
org buffer. This continues ad infinitum.

In the case that I don't want to save progress, this requires making a
new terminal session and sending a sigterm to vim.

—
Reply to this email directly or view it on GitHub
#75.

[alexanderkyte]

:qall! works perfectly. I'm sure what's the difference between the two.
Hooks?

And to reproduce, open up an org buffer and another one, edit both, and
then :q!, :q!, :q!, :q! until you're convinced it's stuck in a cycle.

On Wed, Oct 22, 2014 at 11:03 AM, hsitz [email protected] wrote:

Also, could you check whether the :qall! command works for you in
situation
where you're getting this error? -- Herb

On Wed, Oct 22, 2014 at 7:52 AM, Herbert Sitz [email protected] wrote:

Alexander --

I can't reproduce this behavior. q! works fine for me, in non-org buffer
and in org buffer, regardless of whether edits have been made. Can you
give me a more detailed set of steps to reproduce?

-- Herb

On Wed, Oct 22, 2014 at 7:09 AM, Alexander Kyte <
[email protected]>
wrote:

If I've got multiple buffers open, the second that I open an org file I
lose the ability to :q! out of all of my
buffers. I'm simply told

"No write since last change."

And it switches to the next buffer. :q!-ing this one, moves back to the
org buffer. This continues ad infinitum.

In the case that I don't want to save progress, this requires making a
new terminal session and sending a sigterm to vim.

—
Reply to this email directly or view it on GitHub
#75.

—
Reply to this email directly or view it on GitHub
#75 (comment).

[hsitz]

On Thu, Oct 23, 2014 at 5:51 AM, Alexander Kyte [email protected]
wrote:

:qall! works perfectly. I'm sure what's the difference between the two.
Hooks?

And to reproduce, open up an org buffer and another one, edit both, and
then :q!, :q!, :q!, :q! until you're convinced it's stuck in a cycle.

I do see this behavior, but it doesn't seem tied to there being an org file
in the mix. it does the same thing for me with two sample .txt files.

I assume it's tied to the behavior of q! that will not quit all if last
file in list has unsaved changes. For more info see ':h :q'.