On Tue, Oct 01, 2024 at 01:57:16PM -0400, Richard Kimberly Heck wrote:
> > It's in 601abfe9291.
> >
> > I propose to include it in branch.
>
> Go ahead.
It's in f73b86132c0. Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sat, Sep 28, 2024 at 11:52:04PM -0400, Richard Kimberly Heck wrote:
> On 9/28/24 5:29 PM, Pavel Sanda wrote:
> > On Sat, Sep 28, 2024 at 09:55:04PM +0200, Pavel Sanda wrote:
> > > On Sun, Sep 22, 2024 at 07:11:36PM +0300, Udicoudco wrote:
> > > > The "cololinks" option in the hyperref package di
On 9/28/24 5:29 PM, Pavel Sanda wrote:
On Sat, Sep 28, 2024 at 09:55:04PM +0200, Pavel Sanda wrote:
On Sun, Sep 22, 2024 at 07:11:36PM +0300, Udicoudco wrote:
The "cololinks" option in the hyperref package disables the borders
at the beginning of the document. If you want both you need to add t
On Sat, Sep 28, 2024 at 09:55:04PM +0200, Pavel Sanda wrote:
> On Sun, Sep 22, 2024 at 07:11:36PM +0300, Udicoudco wrote:
> > The "cololinks" option in the hyperref package disables the borders
> > at the beginning of the document. If you want both you need to add the
> > following to the preamble
On Sun, Sep 22, 2024 at 07:11:36PM +0300, Udicoudco wrote:
> The "cololinks" option in the hyperref package disables the borders
> at the beginning of the document. If you want both you need to add the
> following to the preamble after enabling colored links
>
> \AtBeginDocument{\hypersetup{pdfbor
On Sun, Sep 22, 2024 at 07:11:36PM +0300, Udicoudco wrote:
> The "cololinks" option in the hyperref package disables the borders
> at the beginning of the document. If you want both you need to add the
> following to the preamble after enabling colored links
>
> \AtBeginDocument{\hypersetup{pdfbor
whether the GUI should indicate
things similar to the LaTeX implementation or not.
Besides that, these borders are not part of the
printed version, I don't think it is relevant to the
reported problem.
Udi
>
>
>
> ---- Forwarded Message
> Subject: How to underlin
How to underline and color hyperlinks?
Date: Sun, 22 Sep 2024 08:59:28 +
From: Stef Pillaert
To: lyx-users
Something I'm struggling with for a long time now...
A (probably simple?) thing: I don't succeed in giving hyperlinks both a
color _and _underline them.
I want
Am Montag, dem 26.12.2022 um 11:45 -0500 schrieb Richard Kimberly Heck:
> What I was thinking here was that "Other" would more or less act like
> 'literal', in the sense that it would just output whatever's there.
Yes. Would it make more sense to rename this to "Custom"? After all,
it's completely
On 12/26/22 07:21, Jürgen Spitzmüller wrote:
Am Montag, dem 26.12.2022 um 10:26 +0100 schrieb Jürgen Spitzmüller:
Also, I think InsetHyperlink needs to be audited. Now "Web" cares for
"run:" and "[anything]//:" next to the http(s) schemes, "Other" for
all
others expect mail: and file:
Seems not
Am Montag, dem 26.12.2022 um 10:26 +0100 schrieb Jürgen Spitzmüller:
> Also, I think InsetHyperlink needs to be audited. Now "Web" cares for
> "run:" and "[anything]//:" next to the http(s) schemes, "Other" for
> all
> others expect mail: and file:
> Seems not consistent to me. Why is "run:" associ
Am Montag, dem 26.12.2022 um 09:32 +0100 schrieb Jürgen Spitzmüller:
> Am Sonntag, dem 25.12.2022 um 17:53 +0100 schrieb Richard Kimberly
> Heck:
> > +2022-12-25 Richard Kimberly Heck
> > + * Format incremented to 614: New "Other" type for
> > hyperlinks
&
Am Sonntag, dem 25.12.2022 um 17:53 +0100 schrieb Richard Kimberly
Heck:
> +2022-12-25 Richard Kimberly Heck
> + * Format incremented to 614: New "Other" type for hyperlinks
Can you make this entry please a bit more descriptive? Which LyX/LaTeX
correspondence do we hav
On Thu, Aug 27, 2020 at 05:45:34PM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 27.08.2020, 17:30 +0200 schrieb Pavel Sanda:
> > Didn't try yet, but I hope my shell script renamed to .py in $PATH
> > would suffice to work ;)
>
> At least you will need to add (or swallow) the two viewer op
Am Donnerstag, den 27.08.2020, 17:30 +0200 schrieb Pavel Sanda:
> Didn't try yet, but I hope my shell script renamed to .py in $PATH
> would suffice to work ;)
At least you will need to add (or swallow) the two viewer options (-v
and -w) which are now always passed to the script by LyX. And the
sc
On Thu, Aug 27, 2020 at 08:47:55AM +0200, Jürgen Spitzmüller wrote:
> Am Montag, den 24.08.2020, 14:24 +0200 schrieb Jürgen Spitzmüller:
> > Am Montag, den 24.08.2020, 14:08 +0200 schrieb Pavel Sanda:
> > > I saw that coming :)
> > > I am all fine with that, except I don't want to be the one who
>
Am Montag, den 24.08.2020, 14:24 +0200 schrieb Jürgen Spitzmüller:
> Am Montag, den 24.08.2020, 14:08 +0200 schrieb Pavel Sanda:
> > I saw that coming :)
> > I am all fine with that, except I don't want to be the one who
> > is commanded to implement it.
>
> I won't do it either. So let's keep thi
Am Montag, den 24.08.2020, 10:47 -0400 schrieb Richard Kimberly Heck:
> On 8/24/20 8:24 AM, Jürgen Spitzmüller wrote:
> > Am Montag, den 24.08.2020, 14:08 +0200 schrieb Pavel Sanda:
> > > I saw that coming :)
> > > I am all fine with that, except I don't want to be the one who
> > > is commanded to
On 8/24/20 8:24 AM, Jürgen Spitzmüller wrote:
> Am Montag, den 24.08.2020, 14:08 +0200 schrieb Pavel Sanda:
>> I saw that coming :)
>> I am all fine with that, except I don't want to be the one who
>> is commanded to implement it.
> I won't do it either. So let's keep this feature hidden under its
Am Montag, den 24.08.2020, 14:08 +0200 schrieb Pavel Sanda:
> I saw that coming :)
> I am all fine with that, except I don't want to be the one who
> is commanded to implement it.
I won't do it either. So let's keep this feature hidden under its
stone.
Jürgen
signature.asc
Description: This is
On Mon, Aug 24, 2020 at 01:58:47PM +0200, Jürgen Spitzmüller wrote:
> Am Montag, den 24.08.2020, 13:13 +0200 schrieb Pavel Sanda:
> > Tend to think that it has too many assumptions (like naming
> > conventions of the files) that it's generally unlikely to
> > work out of the box for people.
>
> W
Am Montag, den 24.08.2020, 13:13 +0200 schrieb Pavel Sanda:
> Tend to think that it has too many assumptions (like naming
> conventions of the files) that it's generally unlikely to
> work out of the box for people.
We could at least make usage more convenient. As for the naming
conventions: yes,
On Mon, Aug 24, 2020 at 12:58:10PM +0200, Jürgen Spitzmüller wrote:
> Sure, but we COULD make it using it (as we do for the other python
> scripts).
Sorry, misunderstood. I don't have strong opinion about this.
Tend to think that it has too many assumptions (like naming
convetions of the files) t
Am Montag, den 24.08.2020, 12:45 +0200 schrieb Pavel Sanda:
> > A python version could be launched directly from there, though.
>
>
> The run won't be tried unless the RC variable is corretly set by
> configure.py.
>
> And I hope configure won't find it in /share (at least it did not
> find the
On Mon, Aug 24, 2020 at 11:59:00AM +0200, Jürgen Spitzmüller wrote:
> Am Montag, den 24.08.2020, 11:48 +0200 schrieb Pavel Sanda:
> > Correct. The template ends up usually in /usr/share/lyx/scripts/
> > which is not part of standard PATH.
>
> A python version could be launched directly from there,
Am Montag, den 24.08.2020, 11:48 +0200 schrieb Pavel Sanda:
> Correct. The template ends up usually in /usr/share/lyx/scripts/
> which is not part of standard PATH.
A python version could be launched directly from there, though.
In that case, I'd rephrase the menu entry
Item "Try Opening Cited D
On Mon, Aug 24, 2020 at 09:33:19AM +0200, Jürgen Spitzmüller wrote:
> Am Sonntag, den 23.08.2020, 22:23 +0200 schrieb Pavel Sanda:
> > > Ok, adding to my todo list. P
> >
> >
> > there there. p
>
> Am I right that users need to put the script in their paths themselves
> in order to enable it? (i
Am Sonntag, den 23.08.2020, 22:23 +0200 schrieb Pavel Sanda:
> > Ok, adding to my todo list. P
>
>
> there there. p
Am I right that users need to put the script in their paths themselves
in order to enable it? (if so: good)
Jürgen
signature.asc
Description: This is a digitally signed message
On Thu, Aug 20, 2020 at 01:09:06PM +0200, Pavel Sanda wrote:
> On Thu, Aug 20, 2020 at 09:25:00AM +0200, Jürgen Spitzmüller wrote:
> > Am Mittwoch, den 19.08.2020, 21:05 +0200 schrieb Pavel Sanda:
> > > I know, but in that case external script still might be still
> > > succesfull.
> > >
> > > The
On Thu, Aug 20, 2020 at 09:25:00AM +0200, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 19.08.2020, 21:05 +0200 schrieb Pavel Sanda:
> > I know, but in that case external script still might be still
> > succesfull.
> >
> > The only option how to make it disabled for uninterested parties is
> > to p
Am Mittwoch, den 19.08.2020, 21:05 +0200 schrieb Pavel Sanda:
> I know, but in that case external script still might be still
> succesfull.
>
> The only option how to make it disabled for uninterested parties is
> to put lyxpaperview script into configure script.
Yes, please do that. It will be i
On Wed, Aug 19, 2020 at 10:13:56PM -0400, Richard Kimberly Heck wrote:
> I think it's fine to commit, and we can polish it as time permits.
Thanks, initial version committed. P
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 8/19/20 5:34 PM, Pavel Sanda wrote:
> On Tue, Aug 18, 2020 at 10:21:23PM -0400, Richard Kimberly Heck wrote:
>
>>> + if (is_bibtex_) {
>>> + doi = operator[]("doi");
>>> + if (!doi.empty() && !prefixIs(doi,from_ascii("http")))
>>> + doi = "https://doi.org/"; + doi;
>>
On Tue, Aug 18, 2020 at 10:21:23PM -0400, Richard Kimberly Heck wrote:
> This does work with JabRef.
Thanks for testing.
> Space after the "&". Some other places for this, too, and spaces around
> commas.
Fixed.
> > + if (is_bibtex_) {
> > + doi = operator[]("doi");
> > + if (!
On Wed, Aug 19, 2020 at 10:04:36AM +0200, Jürgen Spitzmüller wrote:
> > > > + Item "Open citation content|O" "inset-edit"
> > >
> > > This should be an OptItem, and the function should be disabled if
> > > the
> > > citation in question does not have a target to follow.
> >
> > Not
Am Dienstag, den 18.08.2020, 22:06 +0200 schrieb Pavel Sanda:
> On Tue, Aug 18, 2020 at 09:23:08AM +0200, Jürgen Spitzmüller wrote:
> > > Item "Settings...|S" "inset-settings"
> > > + Item "Open citation content|O" "inset-edit"
> >
> > This should be an OptItem, and t
This does work with JabRef.
> diff --git a/src/BiblioInfo.cpp b/src/BiblioInfo.cpp
> index e37d56389a..a9562c9170 100644
> --- a/src/BiblioInfo.cpp
> +++ b/src/BiblioInfo.cpp
> @@ -651,6 +651,72 @@ docstring const BibTeXInfo::getYear() const
> }
>
>
> +void BibTeXInfo::getLocators(docstring &
On 8/18/20 12:37 PM, Pavel Sanda wrote:
> On Mon, Aug 17, 2020 at 12:19:35PM -0400, Richard Kimberly Heck wrote:
>>> There are several issues:
>>> a) file= field is not standard bibtex, as I understood it's specific for
>>> jabref,
>>>which I do not use. Currenly it will work if full path is g
On Tue, Aug 18, 2020 at 10:20:27AM -0400, Scott Kostyshak wrote:
> One more thing: should the LFUN be disabled if the script is not found
> in the PATH? I'm not suggesting it should be, just asking. If it should,
> should this be done at run time or as part of the configure?
It still should be fun
On Mon, Aug 17, 2020 at 12:19:35PM -0400, Richard Kimberly Heck wrote:
> I see things like:
>
> file =
> {:/home/me/files/other_people/Antony/Antony-BeWhatISay.pdf:PDF},
>
> but also
>
> file = {:Antony-BeWhatISay.pdf:PDF},
>
> if I put the file into the same directory as the bib fi
On Tue, Aug 18, 2020 at 09:23:08AM +0200, Jürgen Spitzmüller wrote:
> > Item "Settings...|S" "inset-settings"
> > + Item "Open citation content|O" "inset-edit"
>
> This should be an OptItem, and the function should be disabled if the
> citation in question does not ha
On Mon, Aug 17, 2020 at 12:19:35PM -0400, Richard Kimberly Heck wrote:
> > There are several issues:
> > a) file= field is not standard bibtex, as I understood it's specific for
> > jabref,
> >which I do not use. Currenly it will work if full path is given but I
> > have
> >no clue what t
On Mon, Aug 17, 2020 at 08:16:44AM +0200, Pavel Sanda wrote:
> On Mon, Aug 17, 2020 at 12:24:07AM -0400, Scott Kostyshak wrote:
> > The script seems to be called whenever I choose *any* option from the
> > context menu, not just the "Open citation content" option.
>
> Should be fixed now.
>
> > R
Only some minor comments. Looks good in general.
Am Montag, den 17.08.2020, 08:16 +0200 schrieb Pavel Sanda:
> diff --git a/lib/ui/stdcontext.inc b/lib/ui/stdcontext.inc
> index c2beb316f4..b47cd4d7f8 100644
> --- a/lib/ui/stdcontext.inc
> +++ b/lib/ui/stdcontext.inc
> @@ -128,6 +128,7 @@ Menuset
On 8/16/20 6:10 PM, Pavel Sanda wrote:
> On Sun, Aug 16, 2020 at 02:21:35PM -0400, Scott Kostyshak wrote:
>> On Sun, Aug 16, 2020 at 04:34:36PM +0200, Pavel Sanda wrote:
>>> On Sun, Aug 16, 2020 at 10:01:22AM -0400, Scott Kostyshak wrote:
I like that idea a lot and would personally find it hel
On Mon, Aug 17, 2020 at 12:24:07AM -0400, Scott Kostyshak wrote:
> The script seems to be called whenever I choose *any* option from the
> context menu, not just the "Open citation content" option.
Should be fixed now.
> Regarding the hardcoding, it's hard to think of an alternative. If we
> stic
On Mon, Aug 17, 2020 at 12:10:24AM +0200, Pavel Sanda wrote:
> Attached is updated patch.
> For a given citation it does:
> 1. check for existence of file= field in bib file, if found launch pdf viewer.
> 2. else check for existence of DOI/URL in bib file. If found launch browser
> with DOI/URL
>
On Sun, Aug 16, 2020 at 02:21:35PM -0400, Scott Kostyshak wrote:
> On Sun, Aug 16, 2020 at 04:34:36PM +0200, Pavel Sanda wrote:
> > On Sun, Aug 16, 2020 at 10:01:22AM -0400, Scott Kostyshak wrote:
>
> > > I like that idea a lot and would personally find it helpful. Here is a
> > > related request,
On Sun, Aug 16, 2020 at 04:34:36PM +0200, Pavel Sanda wrote:
> On Sun, Aug 16, 2020 at 10:01:22AM -0400, Scott Kostyshak wrote:
> > I like that idea a lot and would personally find it helpful. Here is a
> > related request, although not many extra details:
> >
> >
> > https://www.mail-archive.
On Sun, Aug 16, 2020 at 10:01:22AM -0400, Scott Kostyshak wrote:
> > As a somewhat related issue I have very rough code (i.e. intended for my
> > private patchset) which allows viewing papers cited in the document via
> > the context menu of citation inset.
> >
> > ATM it is really shaped for my n
On Fri, Aug 14, 2020 at 07:23:09PM +0200, Pavel Sanda wrote:
> commit 48b1e8a0aca2f3f3faa8f1f800568e47792ba9a0
> Author: Pavel Sanda
> Date: Fri Aug 14 19:46:13 2020 +0200
>
> New attempt on #9906: allow following hyperlinks via context menu.
>
> Now safer ver
attempt on #9906: allow following hyperlinks via context menu.
> >
> > Now safer version with the help of Qt.
>
> As a somewhat related issue I have very rough code (i.e. intended for my
> private patchset) which allows viewing papers cited in the document via
> the con
Scott Kostyshak wrote:
> I am still thinking about implementing this. I'm not yet convinced
> that creating the new type of inset is the best idea. Something more
> simple might get the job done.
>
> The goal is to get the following LaTeX code:
> \hyperlink{refToLabel}{\beamergotobutton{Text on Bu
On Sun, May 12, 2013 at 6:31 AM, Jean-Marc Lasgouttes
wrote:
> Le 07/05/2013 07:54, Scott Kostyshak a écrit :
>
>> On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes
>> wrote:
>>>
>>> We could maybe have an inset that is only a button when no extra text is
>>> needed and a collapsablme inset
Le 07/05/2013 07:54, Scott Kostyshak a écrit :
On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes
wrote:
We could maybe have an inset that is only a button when no extra text is
needed and a collapsablme inset otherwise. Somethin in between InsetCommand
and InsetCollapsable.
How difficult
On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes
wrote:
> We could maybe have an inset that is only a button when no extra text is
> needed and a collapsablme inset otherwise. Somethin in between InsetCommand
> and InsetCollapsable.
How difficult would it be to implement this new inset?
Sc
get, more clearly separating labels
> from hypertargets.
>
> Jürgen, do you still prefer to have the cross ref code copied over to
> the hyperref inset? My hesitation is that there would be a lot of
> duplicate code. Also, I think that the text hyperlinks have more in
> common with re
uped it's easy to navigate) or
there could be a split tree widget, more clearly separating labels
from hypertargets.
Jürgen, do you still prefer to have the cross ref code copied over to
the hyperref inset? My hesitation is that there would be a lot of
duplicate code. Also, I think that th
Le 20/04/2013 09:06, Jürgen Spitzmüller a écrit :
Scott Kostyshak wrote:
Do you think it's better to add \hyperlink support to the label inset
or to make a separate, collapsable hypertarget inset? \hypertarget
takes two arguments: the name and the text. The name could be set in
the settings, and
Scott Kostyshak wrote:
> Do you think it's better to add \hyperlink support to the label inset
> or to make a separate, collapsable hypertarget inset? \hypertarget
> takes two arguments: the name and the text. The name could be set in
> the settings, and the text in the collapsable inset.
I'd pref
On Sun, Apr 14, 2013 at 3:59 AM, Jürgen Spitzmüller wrote:
> Looking at the docs, I'd propose to make beamergotobutton a flex inset within
> beamer.layout. The hyperref inset should be turned into a collapsable inset
> (while the dialog is being kept, minus the "name" field), \hyperlink support
>
On Sun, Apr 14, 2013 at 5:26 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
>> IIUC, when the user makes a hyperlink, either a label or hypertarget
>> label can be hyperlinked to. So all labels and hypertarget labels
>> should be shown in the hyperref inset?
>
> Yes.
I think this is all s
Scott Kostyshak wrote:
> I think I understand most of this. You're suggesting a collapsable
> inset because then the user can insert the beamergotobutton flex inset
> inside of it. The "name" field should be taken out because that is now
> the input to the collapsable inset. To edit the target of t
On Sun, Apr 14, 2013 at 3:59 AM, Jürgen Spitzmüller wrote:
> There is a ticket with a similar request, BTW, but it was resolved wontfix
> (and should be reopened IMHO):
> http://www.lyx.org/trac/ticket/8282
I hadn't seen that ticket. Thanks.
> Looking at the docs, I'd propose to make beamergotob
Scott Kostyshak wrote:
> My next set of questions then:
>
> 1. Are these used outside of Beamer?
\beamergotobutton is, as the name says, a beamer feature. \hyperlink and
\hypertarget, however, are hyperref features, so they can be used in any
document that uses hyperref.
There is a ticket with
On Sun, Apr 14, 2013 at 3:25 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
>> Any thoughts?
>
> I'd go for a.
My next set of questions then:
1. Are these used outside of Beamer?
2. If not, would I need to hardcode these options to only be enabled
when Beamer is being used?
Scott
Scott Kostyshak wrote:
> Any thoughts?
I'd go for a.
Jürgen
e) so many presenters
use text hyperlinks. The text looks like other text so it does not
stand out but it can be clicked on just like a button and just like
one can click on a cross-reference in an article class.
I would like to add support to LyX for these buttons and would like
some advice. Below
Pietro Cortese wrote:
> For example with the code below I'm not able to insert the optional
> argument that should then be transformed into the hypertarget argument.
InsetLayout does not support optional arguments yet. I have some work towards
this in the pipe (for 2.1).
Jürgen
Pol schrieb:
Anyway, in my opinion "http://"; could be added as default protocol, if none
has been specified. That would save time, in case you have to type in the
address.
I implemented this now, please test it out.
regards Uwe
Uwe Stöhr wrote:
>
> What else would you expect? http:// can not be added automatically as most
> users copy/paste Internet addresses from the browser already including
> http://. Note also that you link type could also be ftp:// or another
> Internet protocol.
>
Yes, i see.
Anyway, in my opinion
> Hyperlinks, although entered as of 'Web type', are not translated into http
> addresses, when the pdf file is produced, if the 'http:://' prefix is
> missing in the target field.
> E.g., maxima.sourceforge.met is considred as the name of a local file,
> rath
Hyperlinks, although entered as of 'Web type', are not translated into http
addresses, when the pdf file is produced, if the 'http:://' prefix is
missing in the target field.
E.g., maxima.sourceforge.met is considred as the name of a local file,
rather than an http address.
--
Pol
I am just giving 1.6.0rc1 a try
Here are my first questions:
- I have noticed that the new hyperlink inset is prepending the
tag 'Hyperlink' to the displayed name. Since that tag appears to be
useless, would it be possible to drop it, in the final release?
- The inset "Target" and "Name" hints c
Is there an html converter that will convert the TOC to hyperlinks,
preserving
navigation?
Garst
75 matches
Mail list logo
