On Fri, Aug 10, 2018 at 05:16:56AM +0530, Valmikanathan S wrote:
> Hi,
>
>
>
>
>
> Please find the attached pdf document. Please look into 10th line.
>
>
>
> r(A) = 2 ; r(A) = r(A,B)
>
>
>
> This is not r(A) but rho(A).
I see the problem with your PDF. When I try to compile your
Hi,
Please find the attached pdf document. Please look into 10th line.
r(A) = 2 ; r(A) = r(A,B)
This is not r(A) but rho(A).
Regards
Valmikanathan S
+2 10 Marks_bug report.pdf
Description: Adobe PDF document
+2 10 Marks.lyx
Description: application/lyx
On Thu, Aug 9, 2018 at 9:03 AM, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 09.08.2018, 08:57 -0600 schrieb Joel Kulesza:
> > > We have "Copy as Text" in the info insets context menu.
> >
> > Does that transform the inset to the text values to embed it in the
> > document or copy them to the
Am Donnerstag, den 09.08.2018, 15:57 +0200 schrieb mn:
> On 09.08.18 14:52, Jürgen Spitzmüller wrote:
> >
> > Hm, the file contains info insets (which do not use these glyphs on
> > Linux), not the glyphs itself. But never mind, I've set up a file
> > myself meanwhile.
> >
>
> My bad of a
Am Donnerstag, den 09.08.2018, 08:57 -0600 schrieb Joel Kulesza:
> > We have "Copy as Text" in the info insets context menu.
>
> Does that transform the inset to the text values to embed it in the
> document or copy them to the clipboard?
The latter.
> To serve my purpose vis-a-vis debugging:
On Thu, Aug 9, 2018 at 7:13 AM, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 09.08.2018, 07:07 -0600 schrieb Joel Kulesza:
> > I understand; one could supply both.
>
> But this is not particularly more comfortable than copying text from
> the about LyX dialog.
>
Fine. This is then a
On 09.08.18 14:52, Jürgen Spitzmüller wrote:
>
> Hm, the file contains info insets (which do not use these glyphs on
> Linux), not the glyphs itself. But never mind, I've set up a file
> myself meanwhile.
>
My bad of a mixup. Just in case I attached the proper one.
>> On a Mac these
Am Donnerstag, den 09.08.2018, 07:07 -0600 schrieb Joel Kulesza:
> I understand; one could supply both.
But this is not particularly more comfortable than copying text from
the about LyX dialog.
> However, to keep it as "pure LyX", could one also add an option to
> the info insets to "resolve
On Thu, Aug 9, 2018 at 6:57 AM, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 08.08.2018, 16:36 -0600 schrieb Joel Kulesza:
> > My thought is that this will reduce the (admittedly, minimal) work to
> > characterize/share the user environment information. At present, one
> > must copy/paste text
Am Mittwoch, den 08.08.2018, 16:36 -0600 schrieb Joel Kulesza:
> My thought is that this will reduce the (admittedly, minimal) work to
> characterize/share the user environment information. At present, one
> must copy/paste text or take a screenshot to accompany a MWE.
>
> With this approach,
Am Mittwoch, den 08.08.2018, 19:45 +0200 schrieb mn:
> The attached file contains the problematic symbols that are in
> shortcut.lyx. There might be more in principle.
Hm, the file contains info insets (which do not use these glyphs on
Linux), not the glyphs itself. But never mind, I've set up a
A patch was posted at
https://www.lyx.org/trac/ticket/11241
Maybe someone can have a look.
Daniel
12 matches
Mail list logo
