GNU bug report logs - #5466
Viper opens line in invisible part

Previous Next

To reply to this bug, email your comments to 5466 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Emacs Bugs <bug-gnu-emacs <at> gnu.org>
Subject: Viper opens line in invisible part
Date: Sun, 24 Jan 2010 20:02:12 +0100

If viper-mode is on and you for example in org-mode are in on a header
line with an invisible body and press “o” then the invisible text is
still invisible and point is now in the invisible part.

I think this is a general Emacs problem, not a problem with only Viper
and I suggest that global-reveal-mode is turned on by default.

Message #8 received at 5466 <at> debbugs.gnu.org (full text, mbox):

From: Andrew Hyatt <ahyatt <at> gmail.com>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 5466 <at> debbugs.gnu.org
Subject: Re: bug#5466: Viper opens line in invisible part
Date: Wed, 03 Aug 2016 22:38:08 -0400

Lennart Borgman <lennart.borgman <at> gmail.com> writes:

> If viper-mode is on and you for example in org-mode are in on a header
> line with an invisible body and press “o” then the invisible text is
> still invisible and point is now in the invisible part.
>
> I think this is a general Emacs problem, not a problem with only Viper
> and I suggest that global-reveal-mode is turned on by default.

Sorry for the late reply.  This is still a problem in Emacs 25.

I don't know if I agree that this is a problem, though. The behavior I
see with Viper (or Evil, for that matter) is confusing but not crazy. I
still see that I'm inserting something before the invisible part
(represented by "..."), and when I expand the outline, then my edit
indeed put the text before that invisible part.

Turning on global-reveal-mode by default would change the org experience
and as well, so I'm unsure that is something others would agree on.

Message #11 received at 5466 <at> debbugs.gnu.org (full text, mbox):

From: Andrew Hyatt <ahyatt <at> gmail.com>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 5466 <at> debbugs.gnu.org
Subject: Re: bug#5466: Viper opens line in invisible part
Date: Thu, 18 Aug 2016 00:56:12 -0400

Andrew Hyatt <ahyatt <at> gmail.com> writes:

> Lennart Borgman <lennart.borgman <at> gmail.com> writes:
>
>> If viper-mode is on and you for example in org-mode are in on a header
>> line with an invisible body and press “o” then the invisible text is
>> still invisible and point is now in the invisible part.
>>
>> I think this is a general Emacs problem, not a problem with only Viper
>> and I suggest that global-reveal-mode is turned on by default.
>
> Sorry for the late reply.  This is still a problem in Emacs 25.
>
> I don't know if I agree that this is a problem, though. The behavior I
> see with Viper (or Evil, for that matter) is confusing but not crazy. I
> still see that I'm inserting something before the invisible part
> (represented by "..."), and when I expand the outline, then my edit
> indeed put the text before that invisible part.
>
> Turning on global-reveal-mode by default would change the org experience
> and as well, so I'm unsure that is something others would agree on.

No one has yet disagreed with me, so I'm going to mark this one as a
wishlist - I think there is something that either Org or Viper could do
to work better with each other, but this is more of a feature request
than a bug IMHO.

Message #16 received at 5466 <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Andrew Hyatt <ahyatt <at> gmail.com>
Cc: 5466 <at> debbugs.gnu.org
Subject: Re: bug#5466: Viper opens line in invisible part
Date: Fri, 19 Aug 2016 01:11:25 +0200

[Message part 1 (text/plain, inline)]

It is definitively a bug in my opinion.


On Thu, Aug 18, 2016 at 6:56 AM, Andrew Hyatt <ahyatt <at> gmail.com> wrote:

> Andrew Hyatt <ahyatt <at> gmail.com> writes:
>
> > Lennart Borgman <lennart.borgman <at> gmail.com> writes:
> >
> >> If viper-mode is on and you for example in org-mode are in on a header
> >> line with an invisible body and press “o” then the invisible text is
> >> still invisible and point is now in the invisible part.
> >>
> >> I think this is a general Emacs problem, not a problem with only Viper
> >> and I suggest that global-reveal-mode is turned on by default.
> >
> > Sorry for the late reply.  This is still a problem in Emacs 25.
> >
> > I don't know if I agree that this is a problem, though. The behavior I
> > see with Viper (or Evil, for that matter) is confusing but not crazy. I
> > still see that I'm inserting something before the invisible part
> > (represented by "..."), and when I expand the outline, then my edit
> > indeed put the text before that invisible part.
> >
> > Turning on global-reveal-mode by default would change the org experience
> > and as well, so I'm unsure that is something others would agree on.
>
> No one has yet disagreed with me, so I'm going to mark this one as a
> wishlist - I think there is something that either Org or Viper could do
> to work better with each other, but this is more of a feature request
> than a bug IMHO.
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.