* bug#5466: Viper opens line in invisible part
@ 2010-01-24 19:02 Lennart Borgman
2016-08-04 2:38 ` Andrew Hyatt
0 siblings, 1 reply; 4+ messages in thread
From: Lennart Borgman @ 2010-01-24 19:02 UTC (permalink / raw)
To: 5466
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#5466: Viper opens line in invisible part
2010-01-24 19:02 bug#5466: Viper opens line in invisible part Lennart Borgman
@ 2016-08-04 2:38 ` Andrew Hyatt
2016-08-18 4:56 ` Andrew Hyatt
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Hyatt @ 2016-08-04 2:38 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 5466
Lennart Borgman <lennart.borgman@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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#5466: Viper opens line in invisible part
2016-08-04 2:38 ` Andrew Hyatt
@ 2016-08-18 4:56 ` Andrew Hyatt
2016-08-18 23:11 ` Lennart Borgman
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Hyatt @ 2016-08-18 4:56 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 5466
Andrew Hyatt <ahyatt@gmail.com> writes:
> Lennart Borgman <lennart.borgman@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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#5466: Viper opens line in invisible part
2016-08-18 4:56 ` Andrew Hyatt
@ 2016-08-18 23:11 ` Lennart Borgman
0 siblings, 0 replies; 4+ messages in thread
From: Lennart Borgman @ 2016-08-18 23:11 UTC (permalink / raw)
To: Andrew Hyatt; +Cc: 5466
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
It is definitively a bug in my opinion.
On Thu, Aug 18, 2016 at 6:56 AM, Andrew Hyatt <ahyatt@gmail.com> wrote:
> Andrew Hyatt <ahyatt@gmail.com> writes:
>
> > Lennart Borgman <lennart.borgman@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.
>
[-- Attachment #2: Type: text/html, Size: 2030 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-08-18 23:11 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-24 19:02 bug#5466: Viper opens line in invisible part Lennart Borgman
2016-08-04 2:38 ` Andrew Hyatt
2016-08-18 4:56 ` Andrew Hyatt
2016-08-18 23:11 ` Lennart Borgman
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).