Re: article-koma script

[Guenter Milde]

On 2011-04-14, ozgul sokmen wrote:
 --0016e64618c624178404a0d7c61b
 Content-Type: text/plain; charset=ISO-8859-1

 Hello,
 I have a problem with Koma-Script title page. I would like to see `Abstract`
 title in my output file with `Article-Koma Script `document type. When I
 choose `abstract` environment , I can not see `abstract` title in the output
 file.
 How can i add `abstract` title to my document.
 I appreciate any answer,
 Thanks in advance,

AFAIK, it is a design decision by the KOMA author not to give the
abstract a title in the article class.

You might try with report (KOMA script) or consult the excellent
documentation of the KOMA package in scrguien.pdf.

Günter

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:54 PM, Sam Lewis
stroboscopicallyconflu...@yahoo.co.uk wrote:
 IMO, we need to improve the functionality of
 LyX, and not block good ideas.

 Of course everybody is welcome to make suggestions and put forward ideas on 
 functionality. But it does not mean that everything gets implemented; it 
 needs to be realistic and accepted by the community of users and developers.

... and it needs someone interested and available to actually code the
stuff. :)
Liviu


 Cheers, Sam




-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Stephan Witt]

Am 13.04.2011 um 17:22 schrieb Diego Queiroz:

  I would encourage people to think a few seconds how to call their 
  documents. That will save some time in searching for them later on.
 
 You get the point!
 And how can LyX aid users to achieve this? Yes, you guessed right! Proposing 
 filenames!
 The title is easy to get, but in a higher level of discussion we may also 
 want to discuss if the title/first sentence/etc is the better string to get.
 Maybe some info based on the master document or the document structure? (as 
 Chapter-5, Appendix, etc). I dunno.
 There are lots of things to consider and this basic requested feature could 
 be improved to a most wanted feature.

Nowadays modern desktop systems are providing the capability to search your 
files, e. g. by content.
Normally it is supported by indexing services, so it should give you quick 
answer to
arbitrary questions. Proposing a filename is not such an importing feature, 
IMHO.
And it is not easy to get it right. I' always expect different points of view, 
how this should work.

Stephan

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz queiroz.di...@gmail.com wrote:
 Hellmut, this behavior is not a rule, right?
 As a programmer I assure you: once things are correctly handled, everything
 should be fine. Believe on me. :-)
 And I repeat, it is just a guess for a name to the file, LyX won't impose
 the filename.
 An option to disable this feature is welcome (for those who dislikes).

The LyX coding 'philosophy' is to assist users but in an un-intrusive
manner. To rephrase, we don't intend to provide each and every
disturbingly-helpful feature that MS Word and the ilk provide.
(Personally I find title / first line file name suggestions are
useless for me and provide overhead, since I will always want to
delete that text to provide a file name that confirms to my naming
style. The current 'newfile#.lyx' is always helpful when creating
dummy documents for the ML. I do appreciate, however, that others have
different user habits.)

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!) What is left is to
determine a consistent behaviour that works in most cases for most
users. The current behaviour ('newfile#.lyx') is obviously consistent
and works flawlessly whatever the actual content of the document. The
behaviour you suggest would require coding a contrived hack, which
would take \title if available, otherwise first line (to which some
expressed strong aversion and which I also find disturbing), if
suggestion contains funny chars or delimiters (such as \n \t and the
like) strip them (considering utf-8, how do you determine what is
legal and what is not?), perhaps other difficult to foresee cases
(such as LyX documents containing only ERT).

I know that you will disagree, but I don't think that most users and
developers would approve of such a hack in LyX. And I don't know who
would want to code _and_ maintain it. Regards
Liviu



 If a guess for the filename wasn't necessary, why LyX doesn't leave the file
 field blank instead of newfile?
 The answer is: because this feature improves the software usability.
 Just as an stupid example, suppose I create 10 new files, type something in
 all of them and hit Save all.
 With this feature, I will be able to determine a good name for each file
 (based on the first sentence, or anything else) without navigate to each
 document.
 I bet I can't do the same if newfile or Untitled was the result.
 IMO, we need to improve the functionality of LyX, and not block good ideas.
 ---
 Diego Queiroz



 2011/4/9 Hellmut Weber m...@hellmutweber.de


 Am 08.04.2011 18:37, schrieb Inon Sharony:
  Hey LyX developers!
 
  As in MS (boo!) Office, when saving a new file, whatever appears in the
  \title section should automatically be guessed as the name that the file
  should be saved as.
 
  Do you agree?
 
  Thanks,
 
 Although you addressed the developpers I would like to contribute my
 0.02$ as a user.

 Please do not copy the idiocy of M$ Word to create file names using the
 title or (much worse) the first phrase. This leads in many casesto
 strings which contain blanks or even strnage utf-8 characters.
 Even some windows systems do substitute someof these 'strange'
 characters then by '?' or '_'.


 Best regards

 Hellmut


 --
 Dr. Hellmut Weber         m...@hellmutweber.de
 Degenfeldstraße 2         tel   +49-89-3081172
 D-80803 München-Schwabing mobil +49-172-8450321
 please: No DOCs, no PPTs. why: tinyurl.com/cbgq





-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Walter van Holst]

On Thu, April 14, 2011 10:43, Stephan Witt wrote:
 Nowadays modern desktop systems are providing the capability to search
 your files, e. g. by content.
 Normally it is supported by indexing services, so it should give you
 quick answer to
 arbitrary questions. Proposing a filename is not such an importing
 feature, IMHO.
 And it is not easy to get it right. I' always expect different points
 of view, how this should work.

It definitely is not easy to get 100% right, 80% would be interesting
enough. I disagree on the desktop search bit, that is mostly helpful
if you know a lot about the document you are looking for.

I would find a name-suggester that would take:

The current date, e.g. 20110414, an abbreviation of the style you are
using, for example 'LTR' for letters and the subject of the document
plus a version number

useful.

The most work is probably expanding the various document styles to
include a field that refers to another field that is the most suitable
source for the subject and an abbreviation scheme.

And this assumes of course that people rarely use their own document
styles.

Regards,

 Walter

Re: A basic requested feature

[Diego Queiroz]

 maybe I'm a bit old fashioned (born in 1943 ;-). So I do not have
this terrible need to do everyzhing the fastest way possible.

I'm young (born in the 80's) and I confess I'm neurotic about automatization
(much over the normal). Sorry if I am too boring sometimes.
I enjoy to make the computer decide things for me, and I enjoy much more
when it make good decisions.
BTW, my reseach area is Artificial Intelligence, so how could I think
different? :-)

 ... and it needs someone interested and available to actually code the stuff.
:)

I'm very interested. I have tons of ideas, but I still have problems to set
up a confortable environment to start to code.
Another problem is that I'm still trying to understand some pieces of code,
so it will take some time for me to really contribute with some new feature.

 Proposing a filename is not such an importing feature, IMHO.

I agree.
But this thread subject isn't is list of most important features, it is
just a feature request.
Now if it is important or not, its really another question...

 What is left is to determine a consistent behaviour that works in most
cases for most users. The current behaviour ('newfile#.lyx') is obviously
consistent
and works flawlessly whatever the actual content of the document.

You're probably right. But actually, we really do not know what works in
most cases for most users. We just guess it works for most users.
IMO, this could be a good feature to implement: get statistics of LyX usage
directly from users as other softwares already do (anonymous usage).
Maybe, it is early to think in a thing like this, but it is good to start to
think for the near future (and for god's sake, do not reply me with messages
like I don't think this is the most important feature right now... I know
I know, it is not, ok? :-) ).


Cheers,
---
Diego Queiroz


2011/4/14 Liviu Andronic landronim...@gmail.com

 On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz queiroz.di...@gmail.com
 wrote:
  Hellmut, this behavior is not a rule, right?
  As a programmer I assure you: once things are correctly handled,
 everything
  should be fine. Believe on me. :-)
  And I repeat, it is just a guess for a name to the file, LyX won't impose
  the filename.
  An option to disable this feature is welcome (for those who dislikes).
 
 The LyX coding 'philosophy' is to assist users but in an un-intrusive
 manner. To rephrase, we don't intend to provide each and every
 disturbingly-helpful feature that MS Word and the ilk provide.
 (Personally I find title / first line file name suggestions are
 useless for me and provide overhead, since I will always want to
 delete that text to provide a file name that confirms to my naming
 style. The current 'newfile#.lyx' is always helpful when creating
 dummy documents for the ML. I do appreciate, however, that others have
 different user habits.)

 To be clear, I don't think that LyX will ever care to provide such a
 trivial option in the Prefs. (I hope it won't!) What is left is to
 determine a consistent behaviour that works in most cases for most
 users. The current behaviour ('newfile#.lyx') is obviously consistent
 and works flawlessly whatever the actual content of the document. The
 behaviour you suggest would require coding a contrived hack, which
 would take \title if available, otherwise first line (to which some
 expressed strong aversion and which I also find disturbing), if
 suggestion contains funny chars or delimiters (such as \n \t and the
 like) strip them (considering utf-8, how do you determine what is
 legal and what is not?), perhaps other difficult to foresee cases
 (such as LyX documents containing only ERT).

 I know that you will disagree, but I don't think that most users and
 developers would approve of such a hack in LyX. And I don't know who
 would want to code _and_ maintain it. Regards
 Liviu



  If a guess for the filename wasn't necessary, why LyX doesn't leave the
 file
  field blank instead of newfile?
  The answer is: because this feature improves the software usability.
  Just as an stupid example, suppose I create 10 new files, type something
 in
  all of them and hit Save all.
  With this feature, I will be able to determine a good name for each file
  (based on the first sentence, or anything else) without navigate to each
  document.
  I bet I can't do the same if newfile or Untitled was the result.
  IMO, we need to improve the functionality of LyX, and not block good
 ideas.
  ---
  Diego Queiroz
 
 
 
  2011/4/9 Hellmut Weber m...@hellmutweber.de
 
 
  Am 08.04.2011 18:37, schrieb Inon Sharony:
   Hey LyX developers!
  
   As in MS (boo!) Office, when saving a new file, whatever appears in
 the
   \title section should automatically be guessed as the name that the
 file
   should be saved as.
  
   Do you agree?
  
   Thanks,
  
  Although you addressed the developpers I would like to contribute my
  0.02$ as a user.
 
  Please do not copy the idiocy of M$ Word to create file names using the
  

Re: A basic requested feature

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 14/04/11 11:36, Walter van Holst wrote:
 On Thu, April 14, 2011 10:43, Stephan Witt wrote:
 Nowadays modern desktop systems are providing the capability to search
 your files, e. g. by content.
 Normally it is supported by indexing services, so it should give you
 quick answer to
 arbitrary questions. Proposing a filename is not such an importing
 feature, IMHO.
 And it is not easy to get it right. I' always expect different points
 of view, how this should work.
 
 It definitely is not easy to get 100% right, 80% would be interesting
 enough. I disagree on the desktop search bit, that is mostly helpful
 if you know a lot about the document you are looking for.
 
 I would find a name-suggester that would take:
 
 The current date, e.g. 20110414, an abbreviation of the style you are
 using, for example 'LTR' for letters and the subject of the document
 plus a version number
 
 useful.
 
 The most work is probably expanding the various document styles to
 include a field that refers to another field that is the most suitable
 source for the subject and an abbreviation scheme.
 
 And this assumes of course that people rarely use their own document
 styles.

Interesting suggestion - bug I must agree, it is not an overly iportant
feature. But:

Put it as a feature request into the bug tracker - then it won't be
lost. Then all comments can be there and one could work out a framework
how this could work - I like the different templates for filename an
interesting approach, which could even be used for backups (keep the
last three backups, named following the template provided).

Nice idea - but not that important.

So: Add it to the bug tracker as a feature request then it will not be lost.

Rainer

 
 Regards,
 
  Walter
 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2mxWIACgkQoYgNqgF2egoOTQCeLLT15U+gFo6RmInPzzh5HJzi
AtIAniMqGmBncDog5oRrXFC6vw/5Z+zw
=AeSS
-END PGP SIGNATURE-

Re: A basic requested feature

[Richard Heck]

On 04/14/2011 05:03 AM, Liviu Andronic wrote:

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!)


See the other thread on how there are too many options already!

Richard

input of LaTeX Code

[Rainer Dorsch]

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document 
using ERT and then \input{file.tex}. That worked well. The trouble starts, 
when I do that in a subdocument, which is not in the same directory as the 
toplevel document. Then I need to specify the relative path and that is 
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use 
non-ERT I cannot input a LaTeX file, only LyX files.

Does anybody have a solution for this?

Thanks,
Rainer



-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Re: article-koma script

[stephen's mailinglist account]

 I have a problem with Koma-Script title page. I would like to see `Abstract`
 title in my output file with `Article-Koma Script `document type. When I
 choose `abstract` environment , I can not see `abstract` title in the output
 file.
 How can i add `abstract` title to my document.
 I appreciate any answer,

Provided you are using a recent version of koma-script you can add the
option 'abstract'.

In LyX you add this in Document menu - settings - Document class.
Under class options add abstract into the 'custom' box


-- 
Stephen

Re: input of LaTeX Code

[Richard Heck]

On 04/14/2011 11:03 AM, Rainer Dorsch wrote:

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document
using ERT and then \input{file.tex}. That worked well. The trouble starts,
when I do that in a subdocument, which is not in the same directory as the
toplevel document. Then I need to specify the relative path and that is
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use
non-ERT I cannot input a LaTeX file, only LyX files.

This is because LyX does not know to copy the file to the temporary 
directory when it is done via ERT, and the trick it uses to overcome 
this won't work for documents in different directories. But is there 
some reason you have to use ERT here and not the Include inset?


Richard

Re: Shortcut for math-delim Vert Vert not working

[Richard Heck]

On 04/13/2011 04:35 PM, Pavel Sanda wrote:

Pavel Sanda wrote:

Yang Zhang wrote:

I put this in my user.bind:

\bind M-m M-m S-Bar math-delim Vert Vert

This was actually auto-generated by adding a new shortcut in Tools
Preferences.  But after closing and going back to that Preferences
dialog, instead of Shift-| I see Shift- followed by an (Asian?)
Unicode character.

After looking at the built-in math.bind I changed the above to:

\bind M-m M-m ~C-~M-~S-bar math-delim Vert Vert

This works.  How come?

the problem is in Bar instead of bar. how exactly did you obtain Bar?

maybe from lyx 1.6.x? Richard, we may have new candidate for pref2pref, cf 
#6966, r35797.


Done.

rh

Re: input of LaTeX Code

[Rainer Dorsch]

Am Donnerstag, 14. April 2011 schrieben Sie:
 On 04/14/2011 11:03 AM, Rainer Dorsch wrote:
  Hello,
  
  I do generate a table in LaTeX source format. I included it in a LyX
  document using ERT and then \input{file.tex}. That worked well. The
  trouble starts, when I do that in a subdocument, which is not in the
  same directory as the toplevel document. Then I need to specify the
  relative path and that is different for the subdocument and the toplevel
  document.
  
  When I input files in non-ERT mode, LyX handles this problem. But if I
  use non-ERT I cannot input a LaTeX file, only LyX files.
 
 This is because LyX does not know to copy the file to the temporary
 directory when it is done via ERT, and the trick it uses to overcome
 this won't work for documents in different directories. But is there
 some reason you have to use ERT here and not the Include inset?

Many thanks for the quick reply. 

I did not Insert-File-Child Document. Selected Input there and choose a 
*.tex file. Before I was under the impression I could only include LyX files as 
child documents.

Is that the same as the include inset you are refering to?

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/


signature.asc
Description: This is a digitally signed message part.

Re: Shortcut for math-delim Vert Vert not working

[Pavel Sanda]

Richard Heck wrote:
 Done.

thanks, pavel

Re: article-koma script

[Guenter Milde]

On 2011-04-14, ozgul sokmen wrote:
 --0016e64618c624178404a0d7c61b
 Content-Type: text/plain; charset=ISO-8859-1

 Hello,
 I have a problem with Koma-Script title page. I would like to see `Abstract`
 title in my output file with `Article-Koma Script `document type. When I
 choose `abstract` environment , I can not see `abstract` title in the output
 file.
 How can i add `abstract` title to my document.
 I appreciate any answer,
 Thanks in advance,

AFAIK, it is a design decision by the KOMA author not to give the
abstract a title in the article class.

You might try with report (KOMA script) or consult the excellent
documentation of the KOMA package in scrguien.pdf.

Günter

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:54 PM, Sam Lewis
stroboscopicallyconflu...@yahoo.co.uk wrote:
 IMO, we need to improve the functionality of
 LyX, and not block good ideas.

 Of course everybody is welcome to make suggestions and put forward ideas on 
 functionality. But it does not mean that everything gets implemented; it 
 needs to be realistic and accepted by the community of users and developers.

... and it needs someone interested and available to actually code the
stuff. :)
Liviu


 Cheers, Sam




-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Stephan Witt]

Am 13.04.2011 um 17:22 schrieb Diego Queiroz:

  I would encourage people to think a few seconds how to call their 
  documents. That will save some time in searching for them later on.
 
 You get the point!
 And how can LyX aid users to achieve this? Yes, you guessed right! Proposing 
 filenames!
 The title is easy to get, but in a higher level of discussion we may also 
 want to discuss if the title/first sentence/etc is the better string to get.
 Maybe some info based on the master document or the document structure? (as 
 Chapter-5, Appendix, etc). I dunno.
 There are lots of things to consider and this basic requested feature could 
 be improved to a most wanted feature.

Nowadays modern desktop systems are providing the capability to search your 
files, e. g. by content.
Normally it is supported by indexing services, so it should give you quick 
answer to
arbitrary questions. Proposing a filename is not such an importing feature, 
IMHO.
And it is not easy to get it right. I' always expect different points of view, 
how this should work.

Stephan

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz queiroz.di...@gmail.com wrote:
 Hellmut, this behavior is not a rule, right?
 As a programmer I assure you: once things are correctly handled, everything
 should be fine. Believe on me. :-)
 And I repeat, it is just a guess for a name to the file, LyX won't impose
 the filename.
 An option to disable this feature is welcome (for those who dislikes).

The LyX coding 'philosophy' is to assist users but in an un-intrusive
manner. To rephrase, we don't intend to provide each and every
disturbingly-helpful feature that MS Word and the ilk provide.
(Personally I find title / first line file name suggestions are
useless for me and provide overhead, since I will always want to
delete that text to provide a file name that confirms to my naming
style. The current 'newfile#.lyx' is always helpful when creating
dummy documents for the ML. I do appreciate, however, that others have
different user habits.)

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!) What is left is to
determine a consistent behaviour that works in most cases for most
users. The current behaviour ('newfile#.lyx') is obviously consistent
and works flawlessly whatever the actual content of the document. The
behaviour you suggest would require coding a contrived hack, which
would take \title if available, otherwise first line (to which some
expressed strong aversion and which I also find disturbing), if
suggestion contains funny chars or delimiters (such as \n \t and the
like) strip them (considering utf-8, how do you determine what is
legal and what is not?), perhaps other difficult to foresee cases
(such as LyX documents containing only ERT).

I know that you will disagree, but I don't think that most users and
developers would approve of such a hack in LyX. And I don't know who
would want to code _and_ maintain it. Regards
Liviu



 If a guess for the filename wasn't necessary, why LyX doesn't leave the file
 field blank instead of newfile?
 The answer is: because this feature improves the software usability.
 Just as an stupid example, suppose I create 10 new files, type something in
 all of them and hit Save all.
 With this feature, I will be able to determine a good name for each file
 (based on the first sentence, or anything else) without navigate to each
 document.
 I bet I can't do the same if newfile or Untitled was the result.
 IMO, we need to improve the functionality of LyX, and not block good ideas.
 ---
 Diego Queiroz



 2011/4/9 Hellmut Weber m...@hellmutweber.de


 Am 08.04.2011 18:37, schrieb Inon Sharony:
  Hey LyX developers!
 
  As in MS (boo!) Office, when saving a new file, whatever appears in the
  \title section should automatically be guessed as the name that the file
  should be saved as.
 
  Do you agree?
 
  Thanks,
 
 Although you addressed the developpers I would like to contribute my
 0.02$ as a user.

 Please do not copy the idiocy of M$ Word to create file names using the
 title or (much worse) the first phrase. This leads in many casesto
 strings which contain blanks or even strnage utf-8 characters.
 Even some windows systems do substitute someof these 'strange'
 characters then by '?' or '_'.


 Best regards

 Hellmut


 --
 Dr. Hellmut Weber         m...@hellmutweber.de
 Degenfeldstraße 2         tel   +49-89-3081172
 D-80803 München-Schwabing mobil +49-172-8450321
 please: No DOCs, no PPTs. why: tinyurl.com/cbgq





-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Walter van Holst]

On Thu, April 14, 2011 10:43, Stephan Witt wrote:
 Nowadays modern desktop systems are providing the capability to search
 your files, e. g. by content.
 Normally it is supported by indexing services, so it should give you
 quick answer to
 arbitrary questions. Proposing a filename is not such an importing
 feature, IMHO.
 And it is not easy to get it right. I' always expect different points
 of view, how this should work.

It definitely is not easy to get 100% right, 80% would be interesting
enough. I disagree on the desktop search bit, that is mostly helpful
if you know a lot about the document you are looking for.

I would find a name-suggester that would take:

The current date, e.g. 20110414, an abbreviation of the style you are
using, for example 'LTR' for letters and the subject of the document
plus a version number

useful.

The most work is probably expanding the various document styles to
include a field that refers to another field that is the most suitable
source for the subject and an abbreviation scheme.

And this assumes of course that people rarely use their own document
styles.

Regards,

 Walter

Re: A basic requested feature

[Diego Queiroz]

 maybe I'm a bit old fashioned (born in 1943 ;-). So I do not have
this terrible need to do everyzhing the fastest way possible.

I'm young (born in the 80's) and I confess I'm neurotic about automatization
(much over the normal). Sorry if I am too boring sometimes.
I enjoy to make the computer decide things for me, and I enjoy much more
when it make good decisions.
BTW, my reseach area is Artificial Intelligence, so how could I think
different? :-)

 ... and it needs someone interested and available to actually code the stuff.
:)

I'm very interested. I have tons of ideas, but I still have problems to set
up a confortable environment to start to code.
Another problem is that I'm still trying to understand some pieces of code,
so it will take some time for me to really contribute with some new feature.

 Proposing a filename is not such an importing feature, IMHO.

I agree.
But this thread subject isn't is list of most important features, it is
just a feature request.
Now if it is important or not, its really another question...

 What is left is to determine a consistent behaviour that works in most
cases for most users. The current behaviour ('newfile#.lyx') is obviously
consistent
and works flawlessly whatever the actual content of the document.

You're probably right. But actually, we really do not know what works in
most cases for most users. We just guess it works for most users.
IMO, this could be a good feature to implement: get statistics of LyX usage
directly from users as other softwares already do (anonymous usage).
Maybe, it is early to think in a thing like this, but it is good to start to
think for the near future (and for god's sake, do not reply me with messages
like I don't think this is the most important feature right now... I know
I know, it is not, ok? :-) ).


Cheers,
---
Diego Queiroz


2011/4/14 Liviu Andronic landronim...@gmail.com

 On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz queiroz.di...@gmail.com
 wrote:
  Hellmut, this behavior is not a rule, right?
  As a programmer I assure you: once things are correctly handled,
 everything
  should be fine. Believe on me. :-)
  And I repeat, it is just a guess for a name to the file, LyX won't impose
  the filename.
  An option to disable this feature is welcome (for those who dislikes).
 
 The LyX coding 'philosophy' is to assist users but in an un-intrusive
 manner. To rephrase, we don't intend to provide each and every
 disturbingly-helpful feature that MS Word and the ilk provide.
 (Personally I find title / first line file name suggestions are
 useless for me and provide overhead, since I will always want to
 delete that text to provide a file name that confirms to my naming
 style. The current 'newfile#.lyx' is always helpful when creating
 dummy documents for the ML. I do appreciate, however, that others have
 different user habits.)

 To be clear, I don't think that LyX will ever care to provide such a
 trivial option in the Prefs. (I hope it won't!) What is left is to
 determine a consistent behaviour that works in most cases for most
 users. The current behaviour ('newfile#.lyx') is obviously consistent
 and works flawlessly whatever the actual content of the document. The
 behaviour you suggest would require coding a contrived hack, which
 would take \title if available, otherwise first line (to which some
 expressed strong aversion and which I also find disturbing), if
 suggestion contains funny chars or delimiters (such as \n \t and the
 like) strip them (considering utf-8, how do you determine what is
 legal and what is not?), perhaps other difficult to foresee cases
 (such as LyX documents containing only ERT).

 I know that you will disagree, but I don't think that most users and
 developers would approve of such a hack in LyX. And I don't know who
 would want to code _and_ maintain it. Regards
 Liviu



  If a guess for the filename wasn't necessary, why LyX doesn't leave the
 file
  field blank instead of newfile?
  The answer is: because this feature improves the software usability.
  Just as an stupid example, suppose I create 10 new files, type something
 in
  all of them and hit Save all.
  With this feature, I will be able to determine a good name for each file
  (based on the first sentence, or anything else) without navigate to each
  document.
  I bet I can't do the same if newfile or Untitled was the result.
  IMO, we need to improve the functionality of LyX, and not block good
 ideas.
  ---
  Diego Queiroz
 
 
 
  2011/4/9 Hellmut Weber m...@hellmutweber.de
 
 
  Am 08.04.2011 18:37, schrieb Inon Sharony:
   Hey LyX developers!
  
   As in MS (boo!) Office, when saving a new file, whatever appears in
 the
   \title section should automatically be guessed as the name that the
 file
   should be saved as.
  
   Do you agree?
  
   Thanks,
  
  Although you addressed the developpers I would like to contribute my
  0.02$ as a user.
 
  Please do not copy the idiocy of M$ Word to create file names using the
  

Re: A basic requested feature

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 14/04/11 11:36, Walter van Holst wrote:
 On Thu, April 14, 2011 10:43, Stephan Witt wrote:
 Nowadays modern desktop systems are providing the capability to search
 your files, e. g. by content.
 Normally it is supported by indexing services, so it should give you
 quick answer to
 arbitrary questions. Proposing a filename is not such an importing
 feature, IMHO.
 And it is not easy to get it right. I' always expect different points
 of view, how this should work.
 
 It definitely is not easy to get 100% right, 80% would be interesting
 enough. I disagree on the desktop search bit, that is mostly helpful
 if you know a lot about the document you are looking for.
 
 I would find a name-suggester that would take:
 
 The current date, e.g. 20110414, an abbreviation of the style you are
 using, for example 'LTR' for letters and the subject of the document
 plus a version number
 
 useful.
 
 The most work is probably expanding the various document styles to
 include a field that refers to another field that is the most suitable
 source for the subject and an abbreviation scheme.
 
 And this assumes of course that people rarely use their own document
 styles.

Interesting suggestion - bug I must agree, it is not an overly iportant
feature. But:

Put it as a feature request into the bug tracker - then it won't be
lost. Then all comments can be there and one could work out a framework
how this could work - I like the different templates for filename an
interesting approach, which could even be used for backups (keep the
last three backups, named following the template provided).

Nice idea - but not that important.

So: Add it to the bug tracker as a feature request then it will not be lost.

Rainer

 
 Regards,
 
  Walter
 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2mxWIACgkQoYgNqgF2egoOTQCeLLT15U+gFo6RmInPzzh5HJzi
AtIAniMqGmBncDog5oRrXFC6vw/5Z+zw
=AeSS
-END PGP SIGNATURE-

Re: A basic requested feature

[Richard Heck]

On 04/14/2011 05:03 AM, Liviu Andronic wrote:

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!)


See the other thread on how there are too many options already!

Richard

input of LaTeX Code

[Rainer Dorsch]

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document 
using ERT and then \input{file.tex}. That worked well. The trouble starts, 
when I do that in a subdocument, which is not in the same directory as the 
toplevel document. Then I need to specify the relative path and that is 
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use 
non-ERT I cannot input a LaTeX file, only LyX files.

Does anybody have a solution for this?

Thanks,
Rainer



-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Re: article-koma script

[stephen's mailinglist account]

 I have a problem with Koma-Script title page. I would like to see `Abstract`
 title in my output file with `Article-Koma Script `document type. When I
 choose `abstract` environment , I can not see `abstract` title in the output
 file.
 How can i add `abstract` title to my document.
 I appreciate any answer,

Provided you are using a recent version of koma-script you can add the
option 'abstract'.

In LyX you add this in Document menu - settings - Document class.
Under class options add abstract into the 'custom' box


-- 
Stephen

Re: input of LaTeX Code

[Richard Heck]

On 04/14/2011 11:03 AM, Rainer Dorsch wrote:

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document
using ERT and then \input{file.tex}. That worked well. The trouble starts,
when I do that in a subdocument, which is not in the same directory as the
toplevel document. Then I need to specify the relative path and that is
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use
non-ERT I cannot input a LaTeX file, only LyX files.

This is because LyX does not know to copy the file to the temporary 
directory when it is done via ERT, and the trick it uses to overcome 
this won't work for documents in different directories. But is there 
some reason you have to use ERT here and not the Include inset?


Richard

Re: Shortcut for math-delim Vert Vert not working

[Richard Heck]

On 04/13/2011 04:35 PM, Pavel Sanda wrote:

Pavel Sanda wrote:

Yang Zhang wrote:

I put this in my user.bind:

\bind M-m M-m S-Bar math-delim Vert Vert

This was actually auto-generated by adding a new shortcut in Tools
Preferences.  But after closing and going back to that Preferences
dialog, instead of Shift-| I see Shift- followed by an (Asian?)
Unicode character.

After looking at the built-in math.bind I changed the above to:

\bind M-m M-m ~C-~M-~S-bar math-delim Vert Vert

This works.  How come?

the problem is in Bar instead of bar. how exactly did you obtain Bar?

maybe from lyx 1.6.x? Richard, we may have new candidate for pref2pref, cf 
#6966, r35797.


Done.

rh

Re: input of LaTeX Code

[Rainer Dorsch]

Am Donnerstag, 14. April 2011 schrieben Sie:
 On 04/14/2011 11:03 AM, Rainer Dorsch wrote:
  Hello,
  
  I do generate a table in LaTeX source format. I included it in a LyX
  document using ERT and then \input{file.tex}. That worked well. The
  trouble starts, when I do that in a subdocument, which is not in the
  same directory as the toplevel document. Then I need to specify the
  relative path and that is different for the subdocument and the toplevel
  document.
  
  When I input files in non-ERT mode, LyX handles this problem. But if I
  use non-ERT I cannot input a LaTeX file, only LyX files.
 
 This is because LyX does not know to copy the file to the temporary
 directory when it is done via ERT, and the trick it uses to overcome
 this won't work for documents in different directories. But is there
 some reason you have to use ERT here and not the Include inset?

Many thanks for the quick reply. 

I did not Insert-File-Child Document. Selected Input there and choose a 
*.tex file. Before I was under the impression I could only include LyX files as 
child documents.

Is that the same as the include inset you are refering to?

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/


signature.asc
Description: This is a digitally signed message part.

Re: Shortcut for math-delim Vert Vert not working

[Pavel Sanda]

Richard Heck wrote:
 Done.

thanks, pavel

Re: article-koma script

[Guenter Milde]

On 2011-04-14, ozgul sokmen wrote:
> --0016e64618c624178404a0d7c61b
> Content-Type: text/plain; charset=ISO-8859-1

> Hello,
> I have a problem with Koma-Script title page. I would like to see `Abstract`
> title in my output file with `Article-Koma Script `document type. When I
> choose `abstract` environment , I can not see `abstract` title in the output
> file.
> How can i add `abstract` title to my document.
> I appreciate any answer,
> Thanks in advance,

AFAIK, it is a design decision by the KOMA author not to give the
abstract a title in the article class.

You might try with "report (KOMA script)" or consult the excellent
documentation of the KOMA package in scrguien.pdf.

Günter

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:54 PM, Sam Lewis
 wrote:
>> IMO, we need to improve the functionality of
>> LyX, and not block good ideas.
>
> Of course everybody is welcome to make suggestions and put forward ideas on 
> functionality. But it does not mean that everything gets implemented; it 
> needs to be realistic and accepted by the community of users and developers.
>
... and it needs someone interested and available to actually code the
stuff. :)
Liviu


> Cheers, Sam
>



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Stephan Witt]

Am 13.04.2011 um 17:22 schrieb Diego Queiroz:

> > I would encourage people to think a few seconds how to call their 
> > documents. That will save some time in searching for them later on.
> 
> You get the point!
> And how can LyX aid users to achieve this? Yes, you guessed right! Proposing 
> filenames!
> The title is easy to get, but in a higher level of discussion we may also 
> want to discuss if the title/first sentence/etc is the better string to get.
> Maybe some info based on the master document or the document structure? (as 
> "Chapter-5", "Appendix", etc). I dunno.
> There are lots of things to consider and this "basic requested feature" could 
> be improved to a "most wanted feature".

Nowadays modern desktop systems are providing the capability to search your 
files, e. g. by content.
Normally it is supported by indexing services, so it should give you quick 
answer to
arbitrary questions. Proposing a filename is not such an importing feature, 
IMHO.
And it is not easy to get it right. I' always expect different points of view, 
how this should work.

Stephan

Re: A basic requested feature

[Liviu Andronic]

On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz  wrote:
> Hellmut, this behavior is not a rule, right?
> As a programmer I assure you: once things are correctly handled, everything
> should be fine. Believe on me. :-)
> And I repeat, it is just a guess for a name to the file, LyX won't impose
> the filename.
> An option to disable this feature is welcome (for those who dislikes).
>
The LyX coding 'philosophy' is to assist users but in an un-intrusive
manner. To rephrase, we don't intend to provide each and every
disturbingly-helpful feature that MS Word and the ilk provide.
(Personally I find title / first line file name suggestions are
useless for me and provide overhead, since I will always want to
delete that text to provide a file name that confirms to "my" naming
style. The current 'newfile#.lyx' is always helpful when creating
dummy documents for the ML. I do appreciate, however, that others have
different user habits.)

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!) What is left is to
determine a consistent behaviour that works in most cases for most
users. The current behaviour ('newfile#.lyx') is obviously consistent
and works flawlessly whatever the actual content of the document. The
behaviour you suggest would require coding a contrived hack, which
would take \title if available, otherwise first line (to which some
expressed strong aversion and which I also find disturbing), if
suggestion contains funny chars or delimiters (such as \n \t and the
like) strip them (considering utf-8, how do you determine what is
legal and what is not?), perhaps other difficult to foresee cases
(such as LyX documents containing only ERT).

I know that you will disagree, but I don't think that most users and
developers would approve of such a hack in LyX. And I don't know who
would want to code _and_ maintain it. Regards
Liviu



> If a guess for the filename wasn't necessary, why LyX doesn't leave the file
> field blank instead of "newfile"?
> The answer is: because this feature improves the software usability.
> Just as an stupid example, suppose I create 10 new files, type something in
> all of them and hit "Save all".
> With this feature, I will be able to determine a good name for each file
> (based on the first sentence, or anything else) without navigate to each
> document.
> I bet I can't do the same if "newfile" or "Untitled" was the result.
> IMO, we need to improve the functionality of LyX, and not block good ideas.
> ---
> Diego Queiroz
>
>
>
> 2011/4/9 Hellmut Weber 
>>
>>
>> Am 08.04.2011 18:37, schrieb Inon Sharony:
>> > Hey LyX developers!
>> >
>> > As in MS (boo!) Office, when saving a new file, whatever appears in the
>> > \title section should automatically be guessed as the name that the file
>> > should be saved as.
>> >
>> > Do you agree?
>> >
>> > Thanks,
>> >
>> Although you addressed the developpers I would like to contribute my
>> 0.02$ as a user.
>>
>> Please do not copy the idiocy of M$ Word to create file names using the
>> title or (much worse) the first phrase. This leads in many casesto
>> strings which contain blanks or even strnage utf-8 characters.
>> Even some windows s> characters then by '?' or '_'.
>>
>>
>> Best regards
>>
>> Hellmut
>>
>>
>> --
>> Dr. Hellmut Weber         m...@hellmutweber.de
>> Degenfeldstraße 2         tel   +49-89-3081172
>> D-80803 München-Schwabing mobil +49-172-8450321
>> please: No DOCs, no PPTs. why: tinyurl.com/cbgq
>
>



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: A basic requested feature

[Walter van Holst]

On Thu, April 14, 2011 10:43, Stephan Witt wrote:
> Nowadays modern desktop systems are providing the capability to search
> your files, e. g. by content.
> Normally it is supported by indexing services, so it should give you
> quick answer to
> arbitrary questions. Proposing a filename is not such an importing
> feature, IMHO.
> And it is not easy to get it right. I' always expect different points
> of view, how this should work.

It definitely is not easy to get 100% right, 80% would be interesting
enough. I disagree on the desktop search bit, that is mostly helpful
if you know a lot about the document you are looking for.

I would find a name-suggester that would take:

The current date, e.g. 20110414, an abbreviation of the style you are
using, for example 'LTR' for letters and the subject of the document
plus a version number

useful.

The most work is probably expanding the various document styles to
include a field that refers to another field that is the most suitable
source for the subject and an abbreviation scheme.

And this assumes of course that people rarely use their own document
styles.

Regards,

 Walter

Re: A basic requested feature

[Diego Queiroz]

> maybe I'm a bit old fashioned (born in 1943 ;-). So I do not have
this terrible need to do everyzhing the fastest way possible.

I'm young (born in the 80's) and I confess I'm neurotic about automatization
(much over the normal). Sorry if I am too boring sometimes.
I enjoy to make the computer decide things for me, and I enjoy much more
when it make good decisions.
BTW, my reseach area is Artificial Intelligence, so how could I think
different? :-)

> ... and it needs someone interested and available to actually code the stuff.
:)

I'm very interested. I have tons of ideas, but I still have problems to set
up a confortable environment to start to code.
Another problem is that I'm still trying to understand some pieces of code,
so it will take some time for me to really contribute with some new feature.

> Proposing a filename is not such an importing feature, IMHO.

I agree.
But this thread subject isn't is "list of most important features", it is
just a feature request.
Now if it is important or not, its really another question...

> What is left is to determine a consistent behaviour that works in most
cases for most users. The current behaviour ('newfile#.lyx') is obviously
consistent
and works flawlessly whatever the actual content of the document.

You're probably right. But actually, we really do not know what works in
most cases for most users. We just guess it works for most users.
IMO, this could be a good feature to implement: get statistics of LyX usage
directly from users as other softwares already do (anonymous usage).
Maybe, it is early to think in a thing like this, but it is good to start to
think for the near future (and for god's sake, do not reply me with messages
like "I don't think this is the most important feature right now"... I know
I know, it is not, ok? :-) ).


Cheers,
---
Diego Queiroz


2011/4/14 Liviu Andronic 

> On Wed, Apr 13, 2011 at 3:09 AM, Diego Queiroz 
> wrote:
> > Hellmut, this behavior is not a rule, right?
> > As a programmer I assure you: once things are correctly handled,
> everything
> > should be fine. Believe on me. :-)
> > And I repeat, it is just a guess for a name to the file, LyX won't impose
> > the filename.
> > An option to disable this feature is welcome (for those who dislikes).
> >
> The LyX coding 'philosophy' is to assist users but in an un-intrusive
> manner. To rephrase, we don't intend to provide each and every
> disturbingly-helpful feature that MS Word and the ilk provide.
> (Personally I find title / first line file name suggestions are
> useless for me and provide overhead, since I will always want to
> delete that text to provide a file name that confirms to "my" naming
> style. The current 'newfile#.lyx' is always helpful when creating
> dummy documents for the ML. I do appreciate, however, that others have
> different user habits.)
>
> To be clear, I don't think that LyX will ever care to provide such a
> trivial option in the Prefs. (I hope it won't!) What is left is to
> determine a consistent behaviour that works in most cases for most
> users. The current behaviour ('newfile#.lyx') is obviously consistent
> and works flawlessly whatever the actual content of the document. The
> behaviour you suggest would require coding a contrived hack, which
> would take \title if available, otherwise first line (to which some
> expressed strong aversion and which I also find disturbing), if
> suggestion contains funny chars or delimiters (such as \n \t and the
> like) strip them (considering utf-8, how do you determine what is
> legal and what is not?), perhaps other difficult to foresee cases
> (such as LyX documents containing only ERT).
>
> I know that you will disagree, but I don't think that most users and
> developers would approve of such a hack in LyX. And I don't know who
> would want to code _and_ maintain it. Regards
> Liviu
>
>
>
> > If a guess for the filename wasn't necessary, why LyX doesn't leave the
> file
> > field blank instead of "newfile"?
> > The answer is: because this feature improves the software usability.
> > Just as an stupid example, suppose I create 10 new files, type something
> in
> > all of them and hit "Save all".
> > With this feature, I will be able to determine a good name for each file
> > (based on the first sentence, or anything else) without navigate to each
> > document.
> > I bet I can't do the same if "newfile" or "Untitled" was the result.
> > IMO, we need to improve the functionality of LyX, and not block good
> ideas.
> > ---
> > Diego Queiroz
> >
> >
> >
> > 2011/4/9 Hellmut Weber 
> >>
> >>
> >> Am 08.04.2011 18:37, schrieb Inon Sharony:
> >> > Hey LyX developers!
> >> >
> >> > As in MS (boo!) Office, when saving a new file, whatever appears in
> the
> >> > \title section should automatically be guessed as the name that the
> file
> >> > should be saved as.
> >> >
> >> > Do you agree?
> >> >
> >> > Thanks,
> >> >
> >> Although 

Re: A basic requested feature

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 14/04/11 11:36, Walter van Holst wrote:
> On Thu, April 14, 2011 10:43, Stephan Witt wrote:
>> Nowadays modern desktop systems are providing the capability to search
>> your files, e. g. by content.
>> Normally it is supported by indexing services, so it should give you
>> quick answer to
>> arbitrary questions. Proposing a filename is not such an importing
>> feature, IMHO.
>> And it is not easy to get it right. I' always expect different points
>> of view, how this should work.
> 
> It definitely is not easy to get 100% right, 80% would be interesting
> enough. I disagree on the desktop search bit, that is mostly helpful
> if you know a lot about the document you are looking for.
> 
> I would find a name-suggester that would take:
> 
> The current date, e.g. 20110414, an abbreviation of the style you are
> using, for example 'LTR' for letters and the subject of the document
> plus a version number
> 
> useful.
> 
> The most work is probably expanding the various document styles to
> include a field that refers to another field that is the most suitable
> source for the subject and an abbreviation scheme.
> 
> And this assumes of course that people rarely use their own document
> styles.

Interesting suggestion - bug I must agree, it is not an overly iportant
feature. But:

Put it as a feature request into the bug tracker - then it won't be
lost. Then all comments can be there and one could work out a framework
how this could work - I like the "different templates for filename" an
interesting approach, which could even be used for backups (keep the
last three backups, named following the template provided).

Nice idea - but not that important.

So: Add it to the bug tracker as a feature request then it will not be lost.

Rainer

> 
> Regards,
> 
>  Walter
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2mxWIACgkQoYgNqgF2egoOTQCeLLT15U+gFo6RmInPzzh5HJzi
AtIAniMqGmBncDog5oRrXFC6vw/5Z+zw
=AeSS
-END PGP SIGNATURE-

Re: A basic requested feature

[Richard Heck]

On 04/14/2011 05:03 AM, Liviu Andronic wrote:

To be clear, I don't think that LyX will ever care to provide such a
trivial option in the Prefs. (I hope it won't!)


See the other thread on how there are too many options already!

Richard

input of LaTeX Code

[Rainer Dorsch]

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document 
using ERT and then \input{file.tex}. That worked well. The trouble starts, 
when I do that in a subdocument, which is not in the same directory as the 
toplevel document. Then I need to specify the relative path and that is 
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use 
non-ERT I cannot input a LaTeX file, only LyX files.

Does anybody have a solution for this?

Thanks,
Rainer



-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Re: article-koma script

[stephen's mailinglist account]

>> I have a problem with Koma-Script title page. I would like to see `Abstract`
>> title in my output file with `Article-Koma Script `document type. When I
>> choose `abstract` environment , I can not see `abstract` title in the output
>> file.
>> How can i add `abstract` title to my document.
>> I appreciate any answer,

Provided you are using a recent version of koma-script you can add the
option 'abstract'.

In LyX you add this in Document menu -> settings -> Document class.
Under class options add abstract into the 'custom' box


-- 
Stephen

Re: input of LaTeX Code

[Richard Heck]

On 04/14/2011 11:03 AM, Rainer Dorsch wrote:

Hello,

I do generate a table in LaTeX source format. I included it in a LyX document
using ERT and then \input{file.tex}. That worked well. The trouble starts,
when I do that in a subdocument, which is not in the same directory as the
toplevel document. Then I need to specify the relative path and that is
different for the subdocument and the toplevel document.

When I input files in non-ERT mode, LyX handles this problem. But if I use
non-ERT I cannot input a LaTeX file, only LyX files.

This is because LyX does not know to copy the file to the temporary 
directory when it is done via ERT, and the trick it uses to overcome 
this won't work for documents in different directories. But is there 
some reason you have to use ERT here and not the Include inset?


Richard

Re: Shortcut for "math-delim Vert Vert" not working

[Richard Heck]

On 04/13/2011 04:35 PM, Pavel Sanda wrote:

Pavel Sanda wrote:

Yang Zhang wrote:

I put this in my user.bind:

\bind "M-m M-m S-Bar" "math-delim Vert Vert"

This was actually auto-generated by adding a new shortcut in Tools>
Preferences.  But after closing and going back to that Preferences
dialog, instead of "Shift-|" I see "Shift-" followed by an (Asian?)
Unicode character.

After looking at the built-in math.bind I changed the above to:

\bind "M-m M-m ~C-~M-~S-bar" "math-delim Vert Vert"

This works.  How come?

the problem is in "Bar" instead of "bar". how exactly did you obtain "Bar"?

maybe from lyx 1.6.x? Richard, we may have new candidate for pref2pref, cf 
#6966, r35797.


Done.

rh

Re: input of LaTeX Code

[Rainer Dorsch]

Am Donnerstag, 14. April 2011 schrieben Sie:
> On 04/14/2011 11:03 AM, Rainer Dorsch wrote:
> > Hello,
> > 
> > I do generate a table in LaTeX source format. I included it in a LyX
> > document using ERT and then \input{file.tex}. That worked well. The
> > trouble starts, when I do that in a subdocument, which is not in the
> > same directory as the toplevel document. Then I need to specify the
> > relative path and that is different for the subdocument and the toplevel
> > document.
> > 
> > When I input files in non-ERT mode, LyX handles this problem. But if I
> > use non-ERT I cannot input a LaTeX file, only LyX files.
> 
> This is because LyX does not know to copy the file to the temporary
> directory when it is done via ERT, and the trick it uses to overcome
> this won't work for documents in different directories. But is there
> some reason you have to use ERT here and not the Include inset?

Many thanks for the quick reply. 

I did not Insert->File->Child Document. Selected Input there and choose a 
*.tex file. Before I was under the impression I could only include LyX files as 
child documents.

Is that the same as the include inset you are refering to?

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/


signature.asc
Description: This is a digitally signed message part.

Re: Shortcut for "math-delim Vert Vert" not working

[Pavel Sanda]

Richard Heck wrote:
> Done.

thanks, pavel