GNU bug report logs - #29525
Please don't default to "--unique" mode for Okular

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29525 in the body.
You can then email your comments to 29525 AT debbugs.gnu.org in the normal way.

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

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

From: Reuben Thomas <rrt <at> sc3d.org>
To: bug-auctex <bug-auctex <at> gnu.org>
Subject: Please don't default to "--unique" mode for Okular
Date: Thu, 30 Nov 2017 21:57:36 +0000

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

I'm a long-time user of AUCTeX (thanks, maintainers, for all your work on
it!), and I just started using Okular as my previewer (having found that
Evince 3.18 kept crashing whenever a PDF was updated, most frustrating;
nothing to do with AUCTeX though!).

I noticed that Emacs seemed only ever to start one instance of Okular,
which makes it impossible to view multiple files side-by-side. I tracked
this down to its use of --unique. While there may well be users who prefer
this style, I suggest that it shouldn't be the default in AUCTeX, because
it's not the default for other viewers.

-- 
https://rrt.sc3d.org

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

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

From: Mosè Giordano <mose <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Fri, 1 Dec 2017 19:52:14 +0100

Hi Reuben,

2017-11-30 22:57 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
> I noticed that Emacs seemed only ever to start one instance of Okular, which
> makes it impossible to view multiple files side-by-side. I tracked this down
> to its use of --unique. While there may well be users who prefer this style,

Without this option you'll need to close Okular to view again (C-c
C-v) the document without spawing several instances of the viewer for
the same document.

> I suggest that it shouldn't be the default in AUCTeX, because it's not the
> default for other viewers.

In this regard Evince is smarter than Okular, doesn't create a new
instance for the same document if already open.

I'm not saying the default shouldn't be changed, but I personally like
it because I more often work on a single document rather than multiple
at once.  I'd like to hear comments from other users on this.

Bye,
Mosè

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

From: Arash Esbati <arash <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Fri, 01 Dec 2017 22:49:11 +0100

Reuben Thomas <rrt <at> sc3d.org> writes:

> I noticed that Emacs seemed only ever to start one instance of Okular,
> which makes it impossible to view multiple files side-by-side. I tracked
> this down to its use of --unique. While there may well be users who prefer
> this style, I suggest that it shouldn't be the default in AUCTeX, because
> it's not the default for other viewers.

Hi Reuben,

it is also the default for Yap, dviout, SumatraPDF.  And this is the
problem with defaults: Never 100% satisfied customers.  But this is
Emacs, you can customize everything :-)  Just set your preference in
`TeX-view-program-list' in order to overwrite AUCTeX's default which is
defined in `TeX-view-program-list-builtin'.  E.g., in your .emacs with:

    (setq TeX-view-program-list
          '((Okular" ("okular %o"
                      (mode-io-correlate "#src:%n%a")) "okular")))

Best, Arash

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

From: Reuben Thomas <rrt <at> sc3d.org>
To: Arash Esbati <arash <at> gnu.org>
Cc: 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Sat, 2 Dec 2017 18:52:40 +0000

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

​​Thanks very much to both of you for your feedback.​​

On 1 December 2017 at 21:49, Arash Esbati <arash <at> gnu.org> wrote:

>
> it is also the default for Yap, dviout, SumatraPDF.  And this is the
> problem with defaults: Never 100% satisfied customers.


The problem in this case is not the default per se (though it is hard to
work out how to configure it: the customize interface for this setting is
overcomplicated), it is that the default is different for different
previewers. The default should (as far as possible) be the same, so that
changing viewers does not change the behaviour.

​Mosè said: "Without this option you'll need to close Okular to view again
(C-c C-v) the document without spawing several instances of the viewer for
the same document.​"

This is not exactly true: once Okular (or Evince) has been spawned, there
is no need to run the View command again: both viewers auto-reload.

​So I would be interested to know for how many viewers it's possible to
have this workflow:

1. Start a new instance of a viewer (C-c C-v).

2. Edit the document and reprocess; auto-reload.

If this is possible in most viewers, I suggest it should be the default
setting.

On the other hand, if most viewers use a single instance model, then single
instance should be the default for all viewers that support it.

For the Customize interface, I'm not sure what to suggest. The current
interface is far too complicated, but if it were made simpler (e.g. to have
a "single instance" toggle) then it would not be so general. But as it
stands it seems very hard to use without reading the source code (which
negates the point of customize).

Arash, you mention editing .emacs; this is a shame. It's not the 1990s any
more: I don't even have a .emacs file, I have .emacs.d/init.el; but more to
the point, the default should be to say "customize foo to bar". To advise
editing .emacs is either a) confusing, b) an admission that Customization
isn't manageable, or c) both.

-- 
https://rrt.sc3d.org

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

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

From: Mosè Giordano <mose <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: Arash Esbati <arash <at> gnu.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Sun, 3 Dec 2017 02:13:22 +0100

2017-12-02 19:52 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
> Thanks very much to both of you for your feedback.
>
> On 1 December 2017 at 21:49, Arash Esbati <arash <at> gnu.org> wrote:
>>
>>
>> it is also the default for Yap, dviout, SumatraPDF.  And this is the
>> problem with defaults: Never 100% satisfied customers.
>
>
> The problem in this case is not the default per se (though it is hard to
> work out how to configure it: the customize interface for this setting is
> overcomplicated), it is that the default is different for different
> previewers. The default should (as far as possible) be the same, so that
> changing viewers does not change the behaviour.
>
> Mosè said: "Without this option you'll need to close Okular to view again
> (C-c C-v) the document without spawing several instances of the viewer for
> the same document."
>
> This is not exactly true: once Okular (or Evince) has been spawned, there is
> no need to run the View command again: both viewers auto-reload.

You're saying that it isn't necessary, this doesn't make my previous
statement false --- I mentioned C-c C-v for a reason.  Switching to
the viewer with C-c C-v is what I do, rather than using the window
manager to get to the viewer: I have always several programs open at
the same time, Emacs' and Okular's windows are rarely the closest
ones.  Also, C-c C-a opens the viewer with TeX-view at the end of
compilation, but this is optional.

The more I think about this, the more I'm convinced that the issue you
raised is sensible but the best solution would be to fix first
upstream in Okular.  It'd be a good improvement.  After that, I'll be
more than happy to remove the --unique option.

If you are working with many documents at the same time (say 3-4 or
even more) switching between Emacs and the wanted document can be
really annoying, using C-c C-v brings to focus the right instance of
the viewer.  This is what Evince does and is much more convenient.

> For the Customize interface, I'm not sure what to suggest. The current
> interface is far too complicated, but if it were made simpler (e.g. to have
> a "single instance" toggle) then it would not be so general.

This is an interesting suggestion but probably not so easy to adopt.

> Arash, you mention editing .emacs; this is a shame.

Please, there is no need to put shame on anyone.

> It's not the 1990s any
> more: I don't even have a .emacs file, I have .emacs.d/init.el

I honestly don't get what you mean here.

> but more to
> the point, the default should be to say "customize foo to bar". To advise
> editing .emacs is either a) confusing, b) an admission that Customization
> isn't manageable, or c) both.

Well, he did suggest you to customize `TeX-view-program-list', *and*
provided you, as a possibility, with two lines of code to add to your
init file to accomplish the same task.  It's up to you to decide
what's best for you.  I really don't see what's the problem here.

Bye,
Mosè

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

From: Reuben Thomas <rrt <at> sc3d.org>
To: Mosè Giordano <mose <at> gnu.org>
Cc: Arash Esbati <arash <at> gnu.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Sun, 3 Dec 2017 09:26:02 +0000

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

On 3 December 2017 at 01:13, Mosè Giordano <mose <at> gnu.org> wrote:


> The more I think about this, the more I'm convinced that the issue you
> raised is sensible but the best solution would be to fix first
> upstream in Okular.  It'd be a good improvement.  After that, I'll be
> more than happy to remove the --unique option.
>

I agree that okular should be able to do this.

If you are working with many documents at the same time (say 3-4 or
> even more) switching between Emacs and the wanted document can be
> really annoying, using C-c C-v brings to focus the right instance of
> the viewer.  This is what Evince does and is much more convenient.
>

I agree, but this is a problem to solve with the window manager, not the
application behaviour.

Sometimes, this behaviour of Evince is annoying, because it means I can't
have two views of the same documents (as I can in Emacs, ironically!).


> Please, there is no need to put shame on anyone.
>

​I apologise, I think this was misinterpreted. When in English we say
something is "a shame", this does not mean that anyone should necessarily
"be ashamed".

Well, he did suggest you to customize `TeX-view-program-list', *and*
> provided you, as a possibility, with two lines of code to add to your
> init file to accomplish the same task.  It's up to you to decide
> what's best for you.  I really don't see what's the problem here.
>

​The problem is that this attitude is still common with Emacs package
developers, and it hurts users, especially naive users. We should only talk
about customizing. Because of this "two ways to do it" attitude we have
these problems:

1. Newer users are confused. "Should I use customize or edit .emacs
[whatever that is]?"​ No wonder Emacs seems confusing and complicated.

2. We provide inadequate, incomplete or poor-quality customize interfaces
(as in the present case) because "well, the user can always edit .emacs
instead".

In other programs with a user-editable configuration file, editing the
configuration file is a last resort, when there is something that cannot be
configured in the preferences dialog, or a bug in the program. This should
be true in Emacs too, for all users: customize should be easy for newer
users and convenient for advanced users.

Thanks again. At least, as you observed at the start, what I want is
possible. However, had I not been an Emacs Lisp programmer, I would have
had to ask an expert just to achieve this simple change.

-- 
https://rrt.sc3d.org

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

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

From: Mosè Giordano <mose <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: Arash Esbati <arash <at> gnu.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Sun, 3 Dec 2017 17:32:59 +0100

2017-12-03 10:26 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
>> If you are working with many documents at the same time (say 3-4 or
>> even more) switching between Emacs and the wanted document can be
>> really annoying, using C-c C-v brings to focus the right instance of
>> the viewer.  This is what Evince does and is much more convenient.
>
>
> I agree, but this is a problem to solve with the window manager, not the
> application behaviour.

I don't see how it's a problem of the windows manager.  I happen to
have several programs open at the same time and often switch between
them.  For example, I'm using the terminal, than switch to Emacs and
want to see the output document.  The next window that can be reached
by ALT + TAB is the terminal, not Okular, how could the window manager
guess I want to switch directly to the document viewer?

I missed to stress one important point of C-c C-v: when forward search
is enabled --- and I guess most of us has it on --- C-c C-v moves the
viewer to the corresponding point, this isn't something that can be
achieved by simply switching to the viewer with ALT + TAB.  Thus,
removing the --unique option now would make extremely annoying using
forward search with Okular.

As I already stated, I agree that currently working with multiple
documents can be inconvenient, but breaking usage of forward search
doesn't look a solution to me.  Fixing the behavior of Okular seems a
better approach.  After that, the --unique option is surely not needed
anymore.

Bye,
Mosè

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

From: Arash Esbati <arash <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Sun, 03 Dec 2017 23:15:20 +0100

Reuben Thomas <rrt <at> sc3d.org> writes:

> On 1 December 2017 at 21:49, Arash Esbati <arash <at> gnu.org> wrote:
>
>> it is also the default for Yap, dviout, SumatraPDF.  And this is the
>> problem with defaults: Never 100% satisfied customers.
>
> The problem in this case is not the default per se (though it is hard to
> work out how to configure it: the customize interface for this setting is
> overcomplicated), it is that the default is different for different
> previewers. The default should (as far as possible) be the same, so that
> changing viewers does not change the behaviour.

I agree with this, in this case we should fix this in order to get a
consistent behavior.  I have a preference for the single instance version.

> This is not exactly true: once Okular (or Evince) has been spawned, there
> is no need to run the View command again: both viewers auto-reload.

I don't Okular or Evince, so I can't tell.

> For the Customize interface, I'm not sure what to suggest. The current
> interface is far too complicated, but if it were made simpler (e.g. to have
> a "single instance" toggle) then it would not be so general. But as it
> stands it seems very hard to use without reading the source code (which
> negates the point of customize).

Personally, I think you're touching some darker corners of AUCTeX here.
If you want more complicated stuff, have a look at `TeX-command-list' or
`TeX-expand-list'.  Sometimes it's not easy to reduce complexity to a
minimum.  But again, I might be wrong -- patches are welcome.

> Arash, you mention editing .emacs; this is a shame. It's not the 1990s any
> more: I don't even have a .emacs file, I have .emacs.d/init.el;

From Emacs manual:

,----[ 51.4 The Emacs Initialization File [1] ]
| When Emacs is started, it normally tries to load a Lisp program from an
| initialization file, or init file for short.  This file, if it exists,
| specifies how to initialize Emacs for you.  Emacs looks for your init
| file using the filenames ~/.emacs, ~/.emacs.el, or ~/.emacs.d/init.el;
| you can choose to use any one of these three names (see Find Init).
`----

I don't see it saying that .emacs is obsolete or should be avoided.

> but more to the point, the default should be to say "customize foo to
> bar". To advise editing .emacs is either a) confusing, b) an admission
> that Customization isn't manageable, or c) both.

I just wanted to show you the direction; please use any interface you're
used to or like to use.

Best, Arash

Footnotes: 
[1]  https://www.gnu.org/software/emacs/manual/html_node/emacs/Init-File.html

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

From: Reuben Thomas <rrt <at> sc3d.org>
To: Mosè Giordano <mose <at> gnu.org>
Cc: Arash Esbati <arash <at> gnu.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Mon, 4 Dec 2017 12:58:06 +0000

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

 3 December 2017 at 16:32, Mosè Giordano <mose <at> gnu.org> wrote:

> 2017-12-03 10:26 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
> >> If you are working with many documents at the same time (say 3-4 or
> >> even more) switching between Emacs and the wanted document can be
> >> really annoying, using C-c C-v brings to focus the right instance of
> >> the viewer.  This is what Evince does and is much more convenient.
> >
> >
> > I agree, but this is a problem to solve with the window manager, not the
> > application behaviour.
>
> I don't see how it's a problem of the windows manager.  I happen to
> have several programs open at the same time and often switch between
> them.  For example, I'm using the terminal, than switch to Emacs and
> want to see the output document.  The next window that can be reached
> by ALT + TAB is the terminal, not Okular, how could the window manager
> guess I want to switch directly to the document viewer?
>

I suggest that there are two different things going on here:

1. Should an application be run single-instance, should it raise an
​existing instance if there is one for the same document, or should it
always start a new one? This is a window management problem: it should be
configured in the window manager. The user might prefer different rules for
different apps: for example, one might be more likely to want multiple
windows showing the same document in an editor than in a viewer.

2. In some cases (for example, going back and forth between LaTeX editor
and PDF preview) a more specialised protocol is used. (However, my bug
report was not about this case, it was simply about launching a viewer for
the current file.) In this case, the behaviour should depend on the
protocol (but again, should work the same for different viewers).


> I missed to stress one important point of C-c C-v


​There seems to be some confusion here: you brought up C-c C-v; I didn't
mention it. I was just using the plain "View" command from the C-c C-c
menu. (I guess I should investigate forward search again, though, it's
obviously useful.)​

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

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

From: Reuben Thomas <rrt <at> sc3d.org>
To: Arash Esbati <arash <at> gnu.org>
Cc: 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Mon, 4 Dec 2017 13:06:38 +0000

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

On 3 December 2017 at 22:15, Arash Esbati <arash <at> gnu.org> wrote:

>
> From Emacs manual:
>
> ,----[ 51.4 The Emacs Initialization File [1] ]
> | When Emacs is started, it normally tries to load a Lisp program from an
> | initialization file, or init file for short.  This file, if it exists,
> | specifies how to initialize Emacs for you.  Emacs looks for your init
> | file using the filenames ~/.emacs, ~/.emacs.el, or ~/.emacs.d/init.el;
> | you can choose to use any one of these three names (see Find Init).
> `----
>
> I don't see it saying that .emacs is obsolete or should be avoided.
>

​I think I need to be more precise. Obviously, the init file is not
obsolete: ​it is the way that the custom file is loaded, apart from
anything else! But customize should be the preferred first line of
customization. Chapter 51 starts:

This chapter describes some simple methods to customize the behavior of
Emacs.

   Apart from the methods described here, see *note X Resources:: for
information about using X resources to customize Emacs, and see *note
Keyboard Macros:: for information about recording and replaying keyboard
macros.  Making more far-reaching and open-ended changes involves
writing Emacs Lisp code; see *note Emacs Lisp: (elisp)Top.

​Hence, we as package authors should not be presenting Customization and
.emacs as alternatives: this is just confusing. Like the Emacs manual, use
Customize for easy things, and Emacs Lisp for harder things.

Indeed, where I complained that the AUCTeX interface is too complicated, it
might be better to simplify it to some flags (such as "single instance"),
and require the user to write Lisp code for more complicated cases.  A good
rule of thumb might be: if the Customize interface is harder to understand
than just writing some Lisp, it's not worth having.​ (Just because some
level of configuration can be precisely expressed in a defcustom does not
mean that it should be!)


> ​I ​
> just wanted to show you the direction; please use any interface you're
> used to or like to use.
>

​I am arguing not for myself, but for the way we present Emacs to, in
particular, less-experienced users. Saying "use any interface you're used
to or like" is pleasant, but unhelpful and confusing. It is the sort of
thing that gives Emacs a reputation of being hard to understand and only
for geeks.

-- 
https://rrt.sc3d.org

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

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

From: Mosè Giordano <mose <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: Arash Esbati <arash <at> gnu.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Mon, 4 Dec 2017 17:02:58 +0100

2017-12-04 13:58 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
>> I missed to stress one important point of C-c C-v
>
>
> There seems to be some confusion here: you brought up C-c C-v; I didn't
> mention it. I was just using the plain "View" command from the C-c C-c menu.
> (I guess I should investigate forward search again, though, it's obviously
> useful.)

Yes, there is some confusion: they are the same thing, C-c C-v is
basically a shortcut for C-c C-c View RET RET.

I'm honestly lost.  Could you please explain what's the workflow you'd
like to use?  I thought it's something like this:

1) edit the source in AUCTeX

2) compile it with C-c C-c

3) open the output document in Okular with C-c C-v

4) switch back to Emacs with the window manager (usually ALT + TAB, I guess)

5) edit again

6 compile again with C-c C-c

7) switch to Okular with the window manager.  The document will auto-reload

8) reiterate from point 4

If this is your workflow, forward search can't be used --- C-c C-v is
run only once at point 3 --- unless you close Okular all the time.
Perhaps I'm wrong, so please explain it more clearly.

Bye,
Mosè

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

From: Mosè Giordano <mose <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>, 29525 <at> debbugs.gnu.org
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Tue, 5 Dec 2017 14:04:02 +0100

2017-12-05 13:57 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
>> I'm honestly lost.  Could you please explain what's the workflow you'd
>> like to use?  I thought it's something like this:
>>
>> 1) edit the source in AUCTeX
>>
>> 2) compile it with C-c C-c
>>
>> 3) open the output document in Okular with C-c C-v
>>
>> 4) switch back to Emacs with the window manager (usually ALT + TAB, I
>> guess)
>>
>> 5) edit again
>>
>> 6 compile again with C-c C-c
>>
>> 7) switch to Okular with the window manager.  The document will
>> auto-reload
>>
>> 8) reiterate from point 4
>>
>> If this is your workflow, forward search can't be used --- C-c C-v is
>> run only once at point 3 --- unless you close Okular all the time.
>
>
> This is correct: I am not using forward search. My bug report is simply
> about launching a viewer. My workflow is much simpler: I open the viewer
> once, and after that I let it auto-refresh, changing position in the PDF
> window using its own controls.

Ok, then I'm against making the usage of forward search more
uncomfortable by default.

If Okular will ever get the ability to not open a new instance for an
already open document --- and I really hope so --- the default can be
safely changed.

Bye,
Mosè

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

From: Arash Esbati <arash <at> gnu.org>
To: Mosè Giordano <mose <at> gnu.org>
Cc: 29525 <at> debbugs.gnu.org, Reuben Thomas <rrt <at> sc3d.org>
Subject: Re: bug#29525: Please don't default to "--unique" mode for Okular
Date: Mon, 04 Mar 2024 23:25:45 +0100

Mosè Giordano <mose <at> gnu.org> writes:

> 2017-12-05 13:57 GMT+01:00 Reuben Thomas <rrt <at> sc3d.org>:
>>> I'm honestly lost.  Could you please explain what's the workflow you'd
>>> like to use?  I thought it's something like this:
>>>
>>> 1) edit the source in AUCTeX
>>>
>>> 2) compile it with C-c C-c
>>>
>>> 3) open the output document in Okular with C-c C-v
>>>
>>> 4) switch back to Emacs with the window manager (usually ALT + TAB, I
>>> guess)
>>>
>>> 5) edit again
>>>
>>> 6 compile again with C-c C-c
>>>
>>> 7) switch to Okular with the window manager.  The document will
>>> auto-reload
>>>
>>> 8) reiterate from point 4
>>>
>>> If this is your workflow, forward search can't be used --- C-c C-v is
>>> run only once at point 3 --- unless you close Okular all the time.
>>
>>
>> This is correct: I am not using forward search. My bug report is simply
>> about launching a viewer. My workflow is much simpler: I open the viewer
>> once, and after that I let it auto-refresh, changing position in the PDF
>> window using its own controls.
>
> Ok, then I'm against making the usage of forward search more
> uncomfortable by default.
>
> If Okular will ever get the ability to not open a new instance for an
> already open document --- and I really hope so --- the default can be
> safely changed.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

That said, I think we can mark this report as "wontfix".  Therefore, I'm
closing this report.

Best, Arash

Previous Next

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