Skip to search.

### Breaking NewsVisit Yahoo! News for the latest.

×Close this window

WinEdt

#### Group Information

Already a member? Sign in to Yahoo!

#### Yahoo! Groups Tips

##### Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

### Messages

Advanced
Messages Help
 Messages 11913 - 11942 of 12713   Oldest  |  < Older  |  Newer >  |  Newest
Messages: Show Message Summaries Sort by Date
#11913 From: Agustin E. Bolzán <aebolzan@...>
Date: Fri May 4, 2012 4:20 pm
Subject: Re: Selection
aebolzan@...
Send Email

 Dear Karl, I read your posts and I must say that in any way they have offended me. Agustin Con fecha Viernes, 04 de Mayo de 2012, 01:10:42 p.m., escribió: > Il 04/05/2012 17.29, David Huffer ha scritto: >> First, I did read it. I'm a little annoyed by your tone and, frankly, your tone in a few other posts. That's a bit unnecessary and I'm just about tired of reading your responses and this list in general. Its things like this that make me wonder why I even considered switching from emacs. > David, > don't misunderstand me. My words were not intended to offend you or > anyone else. I was just trying to encourage users to read the manual > because there, as I said, one can learn much about WinEdt's features. >> My default windows behavior respects text color. In every other application I use if unselected text is red then selected text is also red. If unselected text is blue, selected text is also blue. That is the default. Anything else is visually disturbing. > Windows acts the way I said (try Notepad or Wordpad). If your > application has its custom colors, this has nothing to do with Windows > defaults (in fact emacs doesn't use Windows libraries...) >> Thanks for your response, though. It certainly makes my decision to invest in this software an easier one. > I remind you that I'm only a user of WinEdt, as you are, so you don't > make a vexation to me if you switch back to emacs... > Best regards, > Karl

#11914 From: Karl Koeller <karlkoeller@...>
Date: Fri May 4, 2012 5:23 pm
Subject: Re: Selection
karlkoeller@...
Send Email

 Il 04/05/2012 18.20, Agustin E. Bolzán ha scritto: > Dear Karl, > > I read your posts and I must say that in any way they have offended > me. > > Agustin thanks for your remark, Augustin. If anyone (besides David) feels offended by my posts, please let me know. I don't want to offend anyone, but as you all have probably noticed, I'm not very good at speaking English, so I may use words that can offend someone. I don't have any problem to unsubscribe from the list, since I don't have anythink to ask there (maybe I can help someone?). Best regards to all. Karl

#11915 From: WinEdt Team <support@...>
Date: Fri May 4, 2012 7:15 pm
Subject: Re: FW: WinEdt with BiBTeX
support@...
Send Email

 Peter, > 4. So I tried changing line 67 of input.ini to > > PATH="%O;%P;%p;%@('BIBINPUTS');C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib" > > to provide the path to the directory. It made no difference. Assuming that this is the location of your bib file try: PATH="C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib;%O;%P;%p;%@('BIBINPUTS');" and don't forget to load the modified script. \cite{} will work properly once the bib file can be located (it should not have a question mark in the tree). I am not aware of any problems with this functionality. As long as bib file can be found in one of the directories specified in the PATH it works like a charm. In fact, you could just add your custom location in Execution Modes| Variables (BIBINPUTS) without having to modify Input.ini (since %@('BIBINPUTS'); is already included in the default PATH). It is not a common (or good?) practice to put bib (or any other personal data) files inside Program Files directory and you must have changed some permissions to be allowed to do so on Vista or Win7. Make sure that files are actually there and not in Virtual Store which could cause further problems. Best regards, alex

#11916 From: WinEdt Team <support@...>
Date: Fri May 4, 2012 7:16 pm
Subject: Re: Selection
support@...
Send Email

 David, > In Selections.ini I have > > SELECTION="Selected Text" > TEXT_COLOR=-1 > BACKGROUND_RGB="$FABD98" > > and my selections do have that background color. The selected > text, however, is all white. > > What do I need to change to get selected text to retain its > default color? At the moment selections cannot retain highlighted colors because it never crossed my mind to provide an option for that (and this is not the behavior of Windows applications that I am personally familiar with). However, it is absolutely trivial to allow such selections now that we know that some users may prefer it this way... For the next version you can specify TEXT_COLOR=-2 and that means NO text color is associated with this selection mode. It is even possible to do the same for BACKGROUND_COLOR=-2 should one wish to do so. Best regards, alex #11917 From: "McClintock, Peter" <p.v.e.mcclintock@...> Date: Fri May 4, 2012 9:00 pm Subject: RE: FW: WinEdt with BiBTeX p.v.e.mcclintock@... Send Email  Alex, Thank you very much indeed for your advice. Although it has not worked, I have tried a few experiments - 1. Putting PATH="C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib;%O;%P;%p;%@('BIBINPUTS');" into input.ini made no difference. I pressed the "Save" button after making the change, but maybe that was not what you meant by "don't forget to load the modified script"? 2. Putting the path into Execution Modes| Variables (BIBINPUTS) also made no difference. I just put C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib without any other syntax. Was that right? 3. If I move the .bib file to the directory used for the .tex file, then \cite works OK and the question mark in the tree disappears. BiBTeX works too. But that is *not* a convenient place to keep the .bib file. 4. If I put the .bib file anywhere other than (a) with the .tex file or (b) within MiXTeX, BiBTeX stops working because MiXTeX cannot find it when I run "Refresh Filename Database". By the way, the MiXTeX people clearly expect .bib files to be kept within MiXTeX - odd though it may seem - as there is a section of their directory tree specifically for .bib files and another for .bst files. I think this started with version 2.8, or it might have been earlier. Furthermore, if one does not follow this convention, BiBTeX fails (see above). Yes, we got horribly confused by Virtual Store when MiXTeX changed, and we had to start keeping .bib files in the programme area! The problems were eventually resolved by using "Run as Administrator" with both WinEdt and MiXTeX - now standard advice from our IT people and followed throughout this Department. So I remain baffled and rather frustrated - if you have any other thoughts, please advise. Best wishes and thanks again, Peter. -----Original Message----- From: WinEdt Team [mailto:support@...] Sent: 04 May 2012 20:16 To: winedt+list@... Subject: Re: [WinEdt] FW: WinEdt with BiBTeX Peter, > 4. So I tried changing line 67 of input.ini to > > PATH="%O;%P;%p;%@('BIBINPUTS');C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib" > > to provide the path to the directory. It made no difference. Assuming that this is the location of your bib file try: PATH="C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib;%O;%P;%p;%@('BIBINPUTS');" and don't forget to load the modified script. \cite{} will work properly once the bib file can be located (it should not have a question mark in the tree). I am not aware of any problems with this functionality. As long as bib file can be found in one of the directories specified in the PATH it works like a charm. In fact, you could just add your custom location in Execution Modes| Variables (BIBINPUTS) without having to modify Input.ini (since %@('BIBINPUTS'); is already included in the default PATH). It is not a common (or good?) practice to put bib (or any other personal data) files inside Program Files directory and you must have changed some permissions to be allowed to do so on Vista or Win7. Make sure that files are actually there and not in Virtual Store which could cause further problems. Best regards, alex #11918 From: WinEdt Team <support@...> Date: Fri May 4, 2012 10:30 pm Subject: Re: FW: WinEdt with BiBTeX support@... Send Email  Peter, > Thank you very much indeed for your advice. Although it has not > worked, I have tried a few experiments - It works for me. So you must be doing something wrong.. > 1. Putting PATH="C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib;%O;%P;%p;%@('BIBINPUTS');" into input.ini > made no difference. I pressed the "Save" button after making the > change, but maybe that was not what you meant by "don't forget to > load the modified script"? No that's not what I meant. In Help check the section on Options Interface and you will learn how to use it. This is from the relevant Help: IMPORTANT: After you make changes to a particular script you should use the Load Command (the first button in the Option Interface Toolbar) to make the changes effective immediately. It is not necessary to restart WinEdt. In fact, no scripts are loaded at startup: the compiled raw data is stored in WinEdt.dnt (Do Not Touch). This reduces the startup time and reduces the likelihood of error messages during startup. > 2. Putting the path into Execution Modes| Variables (BIBINPUTS) > also made no difference. I just put C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib without any other syntax. Was that right? You must also enable the checkbox in front so that WinEdt actually initializes this variable. After you press apply you should see the correct value in the readonly control below the definition. Do you see this value if you execute: Prompt("%@('BIBINPUTS');"); In Macros -> Define and Run Macro interface? As for the rest: I never run WinEdt as administrator (it is not necessary) and I can put my bib files anywhere I want as long as BIBINPUTS environment variable contains this folder. Both WinEdt and BibTeX will find bib files that are located in any folder listed in BIBINPUTS variable (with MiKTeX 2.9 or TeX Live). Using execution modes to initialize this variable is the simplest way (although it could be done through Windows Control Panel as well). By the way, WinEdt 7 has much better documentation than WinEdt 6 and all this (and more) is actually explained in Help inside Execution Modes| Variables (or Index) even though strictly speaking it is not a WinEdt issue... You can mention this to your IT people once you sort-out Running as Administrator issue (a bad advice if I may say so). I really have nothing else to add. If it still doesn't work I have to give up... Best regards, alex #11919 From: "p. padma Priya" <ppadma.priya@...> Date: Sat May 5, 2012 5:33 am Subject: Re: FW: WinEdt with BiBTeX ppadma.priya@... Send Email  HiHope the \usepackage{} command is present in the file and .bst file is present in the folder along with bib and tex files.RegardsPadma PriyaOn Fri, May 4, 2012 at 9:28 PM, McClintock, Peter wrote: Please can someone advise why my \cite{} does not work properly? Build: 20110218 (v. 6.0), same problem under Windows 7 and Vista 1. If I press "Set main file", \cite{} does not work at all. 2. If I press "Remove main file", \cite{} does work, but very slowly, because the system concatenates an alphabetical list of entries from *all* my .bib files, rather than just the one specified in my .tex document. 3. The left-hand panel (tree) lists correctly the name of my specified .bib file, below the .tex file, but with a "?" to show it cannot find it. 4. So I tried changing line 67 of input.ini to PATH="%O;%P;%p;%@('BIBINPUTS');C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib" to provide the path to the directory. It made no difference. Suggestions will be much appreciated! Peter McClintock. #11920 From: Gyorgy Szeidl <gyorgy.szeidl@...> Date: Sat May 5, 2012 6:45 am Subject: Re: Selection gyorgy.szeidl@... Send Email  dear karl: don't unsubscribe from the list. your messages are aimed at providing help. i am grateful for all the remarks you sent me. in addition i have learnt a lot from the messages you have sent to the list as replies to other list member's questions. english is a second language for me as well, and my knowledge is far away from being a good one. i hope you can understand what i wanted to say. best regards gyorgy > Il 04/05/2012 18.20, Agustin E. Bolzán ha scritto: >> Dear Karl, >> >> I read your posts and I must say that in any way they have offended >> me. >> >> Agustin > > thanks for your remark, Augustin. > > If anyone (besides David) feels offended by my posts, please let me know. > I don't want to offend anyone, but as you all have probably noticed, > I'm not very good at speaking English, so I may use words that can > offend someone. > I don't have any problem to unsubscribe from the list, since I don't > have anythink to ask there (maybe I can help someone?). > > Best regards to all. > > Karl > #11921 From: "McClintock, Peter" <p.v.e.mcclintock@...> Date: Sat May 5, 2012 9:52 am Subject: RE: FW: WinEdt with BiBTeX p.v.e.mcclintock@... Send Email  Padma, Many thanks. Yes, in fact that is all OK. It is a path problem, for which Alex has provided advice that I will now try to put into action. Best wishes, Peter. From: p. padma Priya [mailto:ppadma.priya@...] Sent: 05 May 2012 06:33 To: winedt+list@... Subject: Re: [WinEdt] FW: WinEdt with BiBTeX Hi Hope the \usepackage{} command is present in the file and .bst file is present in the folder along with bib and tex files. Regards Padma Priya On Fri, May 4, 2012 at 9:28 PM, McClintock, Peter wrote: Please can someone advise why my \cite{} does not work properly? Build: 20110218 (v. 6.0), same problem under Windows 7 and Vista 1. If I press "Set main file", \cite{} does not work at all. 2. If I press "Remove main file", \cite{} does work, but very slowly, because the system concatenates an alphabetical list of entries from *all* my .bib files, rather than just the one specified in my .tex document. 3. The left-hand panel (tree) lists correctly the name of my specified .bib file, below the .tex file, but with a "?" to show it cannot find it. 4. So I tried changing line 67 of input.ini to PATH="%O;%P;%p;%@('BIBINPUTS');C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib" to provide the path to the directory. It made no difference. Suggestions will be much appreciated! Peter McClintock. #11922 From: "McClintock, Peter" <p.v.e.mcclintock@...> Date: Sat May 5, 2012 11:03 am Subject: RE: FW: WinEdt with BiBTeX p.v.e.mcclintock@... Send Email  Alex, You were of course correct - I was indeed doing something wrong! All is now "ship-shape"... So thank you again for your patience. Two final questions, if I may - 1. You castigate us for using "Run as Administrator", but MiXTeX apparently *expects* the .bib files to kept in the MiXTeX 2.9\bibtex\bib area prepared for them. As far as I can see, it is then necessary to use WinEdt in Run as Administrator mode in order to edit .bib files there (as otherwise one is apparently editing something virtual). Do you agree? 2. You have shown me how to move my .bib files out of the programme area, which is excellent. But can I also do the same with my .bst files (many of which are also personal files)? Best wishes and thanks again, Peter. -----Original Message----- From: WinEdt Team [mailto:support@...] Sent: 04 May 2012 23:30 To: winedt+list@... Subject: Re: [WinEdt] FW: WinEdt with BiBTeX Peter, > Thank you very much indeed for your advice. Although it has not > worked, I have tried a few experiments - It works for me. So you must be doing something wrong.. > 1. Putting PATH="C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib;%O;%P;%p;%@('BIBINPUTS');" into input.ini made > no difference. I pressed the "Save" button after making the change, > but maybe that was not what you meant by "don't forget to load the > modified script"? No that's not what I meant. In Help check the section on Options Interface and you will learn how to use it. This is from the relevant Help: IMPORTANT: After you make changes to a particular script you should use the Load Command (the first button in the Option Interface Toolbar) to make the changes effective immediately. It is not necessary to restart WinEdt. In fact, no scripts are loaded at startup: the compiled raw data is stored in WinEdt.dnt (Do Not Touch). This reduces the startup time and reduces the likelihood of error messages during startup. > 2. Putting the path into Execution Modes| Variables (BIBINPUTS) also > made no difference. I just put C:\Program Files\MiKTeX > 2.9\bibtex\bib\Peterbib without any other syntax. Was that right? You must also enable the checkbox in front so that WinEdt actually initializes this variable. After you press apply you should see the correct value in the readonly control below the definition. Do you see this value if you execute: Prompt("%@('BIBINPUTS');"); In Macros -> Define and Run Macro interface? As for the rest: I never run WinEdt as administrator (it is not necessary) and I can put my bib files anywhere I want as long as BIBINPUTS environment variable contains this folder. Both WinEdt and BibTeX will find bib files that are located in any folder listed in BIBINPUTS variable (with MiKTeX 2.9 or TeX Live). Using execution modes to initialize this variable is the simplest way (although it could be done through Windows Control Panel as well). By the way, WinEdt 7 has much better documentation than WinEdt 6 and all this (and more) is actually explained in Help inside Execution Modes| Variables (or Index) even though strictly speaking it is not a WinEdt issue... You can mention this to your IT people once you sort-out Running as Administrator issue (a bad advice if I may say so). I really have nothing else to add. If it still doesn't work I have to give up... Best regards, alex #11923 From: Roman <romankal@...> Date: Sat May 5, 2012 2:02 pm Subject: Re: FW: WinEdt with BiBTeX romankal@... Send Email  MiKTeX offers you the ability to create your own TDS, that is, TeX Directory Structure. I would recommend that your local BiB files be placed there rather than in the MiKTeX TDS. [For example, create a root directory, say, \TDS and put your BiB files into \TDS\bibtex\bib. Then execute the MiKTeX Options command, list \TDS as a root directory and refresh the FNDB.] Then updates to MiKTeX will not affect your local files. This use is similar to the WinEdt split between %B and %b. However, I have found that WinEdt doesn't seem to find files in a local \TDS directory even when I specify the path in environment variables. Perhaps there is an access issue. Roman On 5/5/2012 7:03 AM, McClintock, Peter wrote: > Alex, > > You were of course correct - I was indeed doing something wrong! All > is now "ship-shape"... So thank you again for your patience. Two > final questions, if I may - > > 1. You castigate us for using "Run as Administrator", but MiXTeX > apparently *expects* the .bib files to kept in the MiXTeX > 2.9\bibtex\bib area prepared for them. As far as I can see, it is > then necessary to use WinEdt in Run as Administrator mode in order to > edit .bib files there (as otherwise one is apparently editing > something virtual). Do you agree? > > 2. You have shown me how to move my .bib files out of the programme > area, which is excellent. But can I also do the same with my .bst > files (many of which are also personal files)? > > Best wishes and thanks again, > > Peter. > #11924 From: "Simon Platt" <simon@...> Date: Sat May 5, 2012 3:13 pm Subject: Re: Selection simon@... Send Email  I second that. (Apart from the bit about English being a second language, of course.) > dear karl: > don't unsubscribe from the list. your messages are > aimed at providing help. i am grateful for all the remarks > you sent me. in addition i have learnt a lot from the > messages you have sent to the list as replies to other > list member's questions. english is a second language > for me as well, and my knowledge is far away from > being a good one. i hope you can understand what > i wanted to say. > best regards > gyorgy >> Il 04/05/2012 18.20, Agustin E. Bolzán ha scritto: >>> Dear Karl, >>> >>> I read your posts and I must say that in any way they have offended >>> me. >>> >>> Agustin >> >> thanks for your remark, Augustin. >> >> If anyone (besides David) feels offended by my posts, please let me >> know. >> I don't want to offend anyone, but as you all have probably noticed, >> I'm not very good at speaking English, so I may use words that can >> offend someone. >> I don't have any problem to unsubscribe from the list, since I don't >> have anythink to ask there (maybe I can help someone?). >> >> Best regards to all. >> >> Karl >> > > -- Simon Platt #11925 From: Karl Koeller <karlkoeller@...> Date: Sat May 5, 2012 4:05 pm Subject: Re: Selection karlkoeller@... Send Email  Il 05/05/2012 17.13, Simon Platt ha scritto: > I second that. (Apart from the bit about English being a second language, > of course.) > >> dear karl: >> don't unsubscribe from the list. your messages are >> aimed at providing help. i am grateful for all the remarks >> you sent me. in addition i have learnt a lot from the >> messages you have sent to the list as replies to other >> list member's questions. english is a second language >> for me as well, and my knowledge is far away from >> being a good one. i hope you can understand what >> i wanted to say. >> best regards >> gyorgy >>> Il 04/05/2012 18.20, Agustin E. Bolzán ha scritto: >>>> Dear Karl, >>>> >>>> I read your posts and I must say that in any way they have offended >>>> me. >>>> >>>> Agustin >>> thanks for your remark, Augustin. >>> >>> If anyone (besides David) feels offended by my posts, please let me >>> know. >>> I don't want to offend anyone, but as you all have probably noticed, >>> I'm not very good at speaking English, so I may use words that can >>> offend someone. >>> I don't have any problem to unsubscribe from the list, since I don't >>> have anythink to ask there (maybe I can help someone?). >>> >>> Best regards to all. >>> >>> Karl >>> >> > I'm sorry, but I'm afraid I already took a decision about this... I'm sure there is someone kinder than me in the list who's able to answer your questions, anyway. Best regards, Karl #11926 From: "Simon Platt" <simon@...> Date: Sat May 5, 2012 4:20 pm Subject: Re: FW: WinEdt with BiBTeX simon@... Send Email  Roman beat me to it. But in re his "access issue" ... I'm still using WinEdt 6, but I don't experience any such problems. On the machine I'm using now I have BIBINPUTS set to: %@('userprofile');/texmf/bibtex/bib;%@('programfiles');/MikTeX 2.9/bibtex/bib/ieeetran; (set in WinEdt using WinEdt Options/Execution Modes/Variables). I can see files in the local TDS tree (%@('userprofile');/texmf/bibtex/bib) and also in the MikTeX installation tree (%@('programfiles');/MikTeX 2.9/bibtex/bib). I don't think I did anything special to make that happen. I'm using a restricted account under Windows 7 Starter. Simon > MiKTeX offers you the ability to create your own TDS, that is, TeX Directory Structure. I would recommend that your local BiB files be placed there rather than in the MiKTeX TDS. [For example, create a root directory, say, \TDS and put your BiB files into \TDS\bibtex\bib. Then execute the MiKTeX Options command, list \TDS as a root directory and refresh the FNDB.] Then updates to MiKTeX will not affect your local files. This use is similar to the WinEdt split between %B and %b. However, I have found that WinEdt doesn't seem to find files in a local \TDS directory even when I specify the path in environment variables. Perhaps there is an access issue. > Roman > On 5/5/2012 7:03 AM, McClintock, Peter wrote: >> Alex, >> You were of course correct - I was indeed doing something wrong! All is now "ship-shape"... So thank you again for your patience. Two final questions, if I may - >> 1. You castigate us for using "Run as Administrator", but MiXTeX apparently *expects* the .bib files to kept in the MiXTeX >> 2.9\bibtex\bib area prepared for them. As far as I can see, it is then necessary to use WinEdt in Run as Administrator mode in order to edit .bib files there (as otherwise one is apparently editing >> something virtual). Do you agree? >> 2. You have shown me how to move my .bib files out of the programme area, which is excellent. But can I also do the same with my .bst files (many of which are also personal files)? >> Best wishes and thanks again, >> Peter. -- Simon Platt #11927 From: "p. padma Priya" <ppadma.priya@...> Date: Sat May 5, 2012 4:23 pm Subject: Re: FW: WinEdt with BiBTeX ppadma.priya@... Send Email  HiOk. I did not go to the details of Alex's mail. Just saw your concern and replied.ppriyaOn Sat, May 5, 2012 at 3:22 PM, McClintock, Peter wrote: Padma, Many thanks. Yes, in fact that is all OK. It is a path problem, for which Alex has provided advice that I will now try to put into action. Best wishes, Peter. From: p. padma Priya [mailto:ppadma.priya@...] Sent: 05 May 2012 06:33 To: winedt+list@... Subject: Re: [WinEdt] FW: WinEdt with BiBTeX Hi Hope the \usepackage{} command is present in the file and .bst file is present in the folder along with bib and tex files. Regards Padma Priya On Fri, May 4, 2012 at 9:28 PM, McClintock, Peter wrote: Please can someone advise why my \cite{} does not work properly? Build: 20110218 (v. 6.0), same problem under Windows 7 and Vista 1. If I press "Set main file", \cite{} does not work at all. 2. If I press "Remove main file", \cite{} does work, but very slowly, because the system concatenates an alphabetical list of entries from *all* my .bib files, rather than just the one specified in my .tex document. 3. The left-hand panel (tree) lists correctly the name of my specified .bib file, below the .tex file, but with a "?" to show it cannot find it. 4. So I tried changing line 67 of input.ini to PATH="%O;%P;%p;%@('BIBINPUTS');C:\Program Files\MiKTeX 2.9\bibtex\bib\Peterbib" to provide the path to the directory. It made no difference. Suggestions will be much appreciated! Peter McClintock. #11928 From: "McClintock, Peter" <p.v.e.mcclintock@...> Date: Sat May 5, 2012 7:09 pm Subject: RE: FW: WinEdt with BiBTeX p.v.e.mcclintock@... Send Email  Dear Simon and Roman, Thank you very much indeed for your helpful advice and for taking the trouble to write! Much appreciated. Best wishes, Peter. -----Original Message----- From: Simon Platt [mailto:simon@...] Sent: 05 May 2012 17:21 To: winedt+list@... Subject: Re: [WinEdt] FW: WinEdt with BiBTeX Roman beat me to it. But in re his "access issue" ... I'm still using WinEdt 6, but I don't experience any such problems. On the machine I'm using now I have BIBINPUTS set to: %@('userprofile');/texmf/bibtex/bib;%@('programfiles');/MikTeX 2.9/bibtex/bib/ieeetran; (set in WinEdt using WinEdt Options/Execution Modes/Variables). I can see files in the local TDS tree (%@('userprofile');/texmf/bibtex/bib) and also in the MikTeX installation tree (%@('programfiles');/MikTeX 2.9/bibtex/bib). I don't think I did anything special to make that happen. I'm using a restricted account under Windows 7 Starter. Simon > MiKTeX offers you the ability to create your own TDS, that is, TeX Directory Structure. I would recommend that your local BiB files be placed there rather than in the MiKTeX TDS. [For example, create a root directory, say, \TDS and put your BiB files into \TDS\bibtex\bib. Then execute the MiKTeX Options command, list \TDS as a root directory and refresh the FNDB.] Then updates to MiKTeX will not affect your local files. This use is similar to the WinEdt split between %B and %b. However, I have found that WinEdt doesn't seem to find files in a local \TDS directory even when I specify the path in environment variables. Perhaps there is an access issue. > Roman > On 5/5/2012 7:03 AM, McClintock, Peter wrote: >> Alex, >> You were of course correct - I was indeed doing something wrong! All >> is now "ship-shape"... So thank you again for your patience. Two final questions, if I may - >> 1. You castigate us for using "Run as Administrator", but MiXTeX apparently *expects* the .bib files to kept in the MiXTeX >> 2.9\bibtex\bib area prepared for them. As far as I can see, it is >> then necessary to use WinEdt in Run as Administrator mode in order to edit .bib files there (as otherwise one is apparently editing >> something virtual). Do you agree? >> 2. You have shown me how to move my .bib files out of the programme area, which is excellent. But can I also do the same with my .bst files (many of which are also personal files)? >> Best wishes and thanks again, >> Peter. -- Simon Platt #11929 From: James Melton <james.douglas.melton@...> Date: Mon May 7, 2012 11:18 am Subject: Help Writing Macro for LaTeXdiff james.douglas.melton@... Send Email  Hello all, I am hoping someone can help me (an inexperienced macro writer) with a macro that I am trying to write for WinEdt 5.5 begin run on a PC with Windows 7 Home Premium (Service Pack 1). Basically, I am trying to write a macro that automates the use of latexdiff, a program used to analyze the differences between two .tex files. Normally, one would need to do the following to run latexdiff (after downloading the program and Perl): 1. open the command prompt 2. enter the following: latexdiff file1.tex file2.tex> diff.tex 3. open the diff.tex file 4. compile the .tex file to create a .pdf I want to write a macro that automates this process. Here is the code I wrote: Browse(0,"TeX|*.tex|All Files|*.*","%p"); GetFileName("%!0", 0); SetFolder("%p"); Run('latexdiff.exe "%n.tex" "%!0.tex"> "%n_track.tex"','%p'); Open("%n_track.tex"); Exe('%b\Exec\MikTeX\PDFTeXify.edt'); There seems to be a problem with the run command. When I run the macro, I get the following error: "2 and only 2 non-option arguments required. Write latexdiff -h to get help". This is the error latexdiff gives when the there are more than or less than 2 files listed to compare (i.e. if I type just "latexdiff" or "latexdiff file1.tex file2.tex file3.tex" at the command line), which leads me to believe that there is something wrong with this part of the run command: "%n.tex" "%!0.tex"> "%n_track.tex" (note that I have also tried the command without the quotes around the file names and using only single quotes around the file names). The problem is that I do not know how to fix it. Any help the members of this list can provide would be greatly appreciated! Thanks! James NOTE: For time being, I wrote the following two macros, which work when pasting the command copied to the clipboard into the opened command line: latexdiff.edt: Browse(0,"TeX|*.tex|All Files|*.*","%p"); GetFileName("%!0", 0); SetFolder("%p"); CopyToClipboard("latexdiff.exe %n.tex %!0.tex> %n_track.tex",0); Run('%$("CMD");','%!P',0,0,'%$("CMDTitle");',1,1); opendiff.edt: SetFolder("%p"); Open("%n_track.tex"); Exe('%b\Exec\MikTeX\PDFTeXify.edt'); -- ***************************************** James Melton Assistant Professor IMT Institute for Advanced Studies james.melton@... https://netfiles.uiuc.edu/melton ***************************************** #11930 From: WinEdt Team <support@...> Date: Mon May 7, 2012 5:55 pm Subject: Re: Help Writing Macro for LaTeXdiff support@... Send Email  James, There is nothing wrong with Run macro. However, you cannot use cmd.exe (Command Prompt) syntax (< or >) to redirect input or output. Thus Run('latexdiff.exe "%n.tex" "%!0.tex"> "%n_track.tex"','%p'); will not work! The > portion only works if it is interpreted by cmd.exe directly... Furthermore, you should also specify Wait for Execution to Finish parameter to properly synchronize the execution sequence. You have three options: 1. use WinExe macro that can redirect output. This is a bit more complicated but documented in Help and it will work if done properly. I'll skip the details as I don't have latexdiff.exe and I don't have WinEdt 5.5 on this machine either. 2. Write a batch file that executes latexdiff.exe within command prompt (with the command that you use in cmd.exe) and use Run macro (with Wait parameter set to 1) to execute this batch file instead of latexdiff.exe directly: Run('latexdiff.bat "%n" "%!0"','%p', 0,0,"",0,0,1); Help lists all parameters for Run or WinExe. Your batch file will need two parameters that will be seen as %1 and %2 inside its command line. That's all... 3. Check cmd.exe /? (to learn what switches you can pass to Windows command prompt) and then you can try something like: Run('cmd.exe /C latexdiff.exe "%n.tex" "%!0.tex"> "%n_track.tex"','%p'); Best regards, alex #11931 From: Sotiris Fragkiskos <sfranky@...> Date: Mon May 7, 2012 6:09 pm Subject: Re: Help Writing Macro for LaTeXdiff sfranky@... Send Email  ... and then send it to winedt.org so that we can all enjoy it :) #11932 From: James Melton <james.douglas.melton@...> Date: Tue May 8, 2012 6:12 am Subject: Re: Help Writing Macro for LaTeXdiff james.douglas.melton@... Send Email  Thanks for your help Alex! When I get a chance, I will submit the macro to WinEdt.org for others to use. In the meantime, here is the resulting macro: IfStr("%t",".tex","=","",'CMD("Open...");'); Browse(0,"TeX|*.tex|All Files|*.*","%p"); GetFileName("%!0", 0); Run('cmd.exe /C latexdiff.exe %!0.tex %n.tex > %n_diff.tex','%p',0,0,"",0,0,1); Open("%p\%n_diff.tex"); Exe('%b\Exec\MikTeX\PDFTeXify.edt'); For those of you unfamiliar with the macro language, here is what it does: 1) finds the "new" version of the file, either the active tab (in WinEdt 5.5) or, if a .tex file is not the active tab, then the Open... command is run 2) browses for the "old" version of the file (Note that the old and new versions of the file should be in the same directory, which is fine for the way I handle file versions but may not work well for others. I tried to relax this requirement but received an error.) 3) runs latexdiff 4) opens the resulting _diff.tex file 5) executes PDFTeXify Best, James ***************************************** James Melton Assistant Professor IMT Institute for Advanced Studies james.melton@... https://netfiles.uiuc.edu/melton ***************************************** #11933 From: "p. padma Priya" <ppadma.priya@...> Date: Tue May 8, 2012 10:45 am Subject: Re: Help Writing Macro for LaTeXdiff ppadma.priya@... Send Email  HiPlease send to winedt.org too.Please let me know to include this package in winedt. I use ver. 7.ppriyaOn Mon, May 7, 2012 at 11:25 PM, WinEdt Team wrote: James, There is nothing wrong with Run macro. However, you cannot use cmd.exe (Command Prompt) syntax (< or >) to redirect input or output. Thus Run('latexdiff.exe "%n.tex" "%!0.tex"> "%n_track.tex"','%p'); will not work! The > portion only works if it is interpreted by cmd.exe directly... Furthermore, you should also specify Wait for Execution to Finish parameter to properly synchronize the execution sequence. You have three options: 1. use WinExe macro that can redirect output. This is a bit more complicated but documented in Help and it will work if done properly. I'll skip the details as I don't have latexdiff.exe and I don't have WinEdt 5.5 on this machine either. 2. Write a batch file that executes latexdiff.exe within command prompt (with the command that you use in cmd.exe) and use Run macro (with Wait parameter set to 1) to execute this batch file instead of latexdiff.exe directly: Run('latexdiff.bat "%n" "%!0"','%p', 0,0,"",0,0,1); Help lists all parameters for Run or WinExe. Your batch file will need two parameters that will be seen as %1 and %2 inside its command line. That's all... 3. Check cmd.exe /? (to learn what switches you can pass to Windows command prompt) and then you can try something like: Run('cmd.exe /C latexdiff.exe "%n.tex" "%!0.tex"> "%n_track.tex"','%p'); Best regards, alex #11934 From: Karl Koeller <karlkoeller@...> Date: Wed May 9, 2012 4:38 am Subject: NEW - WinEdt 7 contribution: ANSI2UTF8 karlkoeller@... Send Email  Dear WinEdt-ers, This WinEdt 7 contribution may be of interest for: - Users that want to convert their old ANSI documents to UTF-8 with a click. Visit http://www.winedt.org/Config/menus/ANSI2UTF8.php for more info and download. Regards, KarlPS: Contact me privately for further help. #11935 From: Zulkifli Hidayat <zhidayat@...> Date: Wed May 9, 2012 9:19 am Subject: Alt+arrow bug? zhidayat@... Send Email  Dear Alex, It seems that I find a bug in Winedt 7 Build: 20120423 when using Alt+arrow for the document below. Soft-returns mode: a. Block the table from the first \hline to the last \hline. b. Move the text with Alt+right arrow: the last \hline will be eaten from the right c. Move the text with Alt+left arrow: the first \hline will be eaten from the left In hard-returns mode: c. All lines will be eaten from the left Best, -Zul- \documentclass{article} \begin{document} \begin{table} \centering \caption{A table} \begin{tabular}{cccccc} \hline 1 & ($x,y,z$) & \# & ($x,y,z$) & \# & ($x,y,z$) \\ \hline 2 &$x,y,z$& 14 &$x,y,z$& 21 &$x,y,z$\\ 3 &$x,y,z$& 15 &$x,y,z$& 22 &$x,y,z\$ \\ \hline \end{tabular} \end{table} \end{document}

#11936 From: Gyorgy SZEIDL <gyorgy.szeidl@...>
Date: Wed May 9, 2012 10:40 am
Subject: winedt does not save the changes i have made in a dictionary
gyorgy.szeidl@...
Send Email

 dear list members: i have just installed winedt 7 on a new pc (this is going to be my new home computer). operating system is windows 7 (64Bit). if i add a new word to my hungarian dictionary everything is OK. however when i close the program i have an error message: Error saving dictionary etc. the same installation works fine on my laptop under windows 7 (32bit). i think windows parameters should be changed in order to make possible that winedt could save the changes in my hungarian dictionary. please help, i have no idea what to do. best regards gyorgy

#11937 From: Hanno Dierke <h.dierke@...>
Date: Wed May 9, 2012 11:06 am
Subject: Re: winedt does not save the changes i have made in a dictionary
h.dierke@...
Send Email

 Gyorgy, I guess your dictionary is in the Program Files folder (like e.g. C:\Program files (x86)\WinEdt Team\WinEdt 7\Dict)? In Windows 7 there are some restrictions for the program folders, so you might want to put the dictionaries you want to modify in your personal documents folder or some other folder where you have write permissions. Best regards Hanno Am 09.05.2012 12:40, schrieb Gyorgy SZEIDL: > dear list members: > > i have just installed winedt 7 on a new > pc (this is going to be my new home computer). > operating system is windows 7 (64Bit). if i add a > new word to my hungarian dictionary everything > is OK. however when i close the program i have > an error message: > > Error saving dictionary etc. > > the same installation works fine on my laptop > under windows 7 (32bit). > i think windows parameters should be changed > in order to make possible that winedt could save > the changes in my hungarian dictionary. > > please help, i have no idea what to do. > > best regards > gyorgy > > > > -- Dr. Hanno Dierke TU Braunschweig Institut für Produktionsmesstechnik Schleinitzstr. 20 38106 Braunschweig Tel. 0531/391-7048 Fax 0531/391-5837 eMail: h.dierke@...

#11938 From: "McClintock, Peter" <p.v.e.mcclintock@...>
Date: Wed May 9, 2012 11:11 am
Subject: RE: winedt does not save the changes i have made in a dictionary
p.v.e.mcclintock@...
Send Email

 Gyorgy, Probably, if you start WinEdt with a right-click, and then "Run as Administrator", your editing problem will go away. (But Alex considers this to be rather a dubious practice for getting round Windows access problems!) Best wishes, Peter. -----Original Message----- From: Hanno Dierke [mailto:h.dierke@...] Sent: 09 May 2012 12:07 To: winedt+list@... Subject: Re: [WinEdt] winedt does not save the changes i have made in a dictionary Gyorgy, I guess your dictionary is in the Program Files folder (like e.g. C:\Program files (x86)\WinEdt Team\WinEdt 7\Dict)? In Windows 7 there are some restrictions for the program folders, so you might want to put the dictionaries you want to modify in your personal documents folder or some other folder where you have write permissions. Best regards Hanno Am 09.05.2012 12:40, schrieb Gyorgy SZEIDL: > dear list members: > > i have just installed winedt 7 on a new pc (this is going to be my new > home computer). > operating system is windows 7 (64Bit). if i add a new word to my > hungarian dictionary everything is OK. however when i close the > program i have an error message: > > Error saving dictionary etc. > > the same installation works fine on my laptop under windows 7 (32bit). > i think windows parameters should be changed in order to make possible > that winedt could save the changes in my hungarian dictionary. > > please help, i have no idea what to do. > > best regards > gyorgy > > > > -- Dr. Hanno Dierke TU Braunschweig Institut für Produktionsmesstechnik Schleinitzstr. 20 38106 Braunschweig Tel. 0531/391-7048 Fax 0531/391-5837 eMail: h.dierke@...

#11939 From: Gyorgy SZEIDL <gyorgy.szeidl@...>
Date: Wed May 9, 2012 11:21 am
Subject: Re: winedt does not save the changes i have made in a dictionary
gyorgy.szeidl@...
Send Email

 hi peter: thank you very much: this has solved the problem. i am also grateful to hanno for suggesting a further solution. thank you once again. best regards gyorgy > Gyorgy, > > Probably, if you start WinEdt with a right-click, and then "Run as Administrator", your editing problem will go away. (But Alex considers this to be rather a dubious practice for getting round Windows access problems!) > > Best wishes, > > Peter. > > -----Original Message----- > From: Hanno Dierke [mailto:h.dierke@...] > Sent: 09 May 2012 12:07 > To: winedt+list@... > Subject: Re: [WinEdt] winedt does not save the changes i have made in a dictionary > > Gyorgy, > > I guess your dictionary is in the Program Files folder (like e.g. > C:\Program files (x86)\WinEdt Team\WinEdt 7\Dict)? In Windows 7 there are some restrictions for the program folders, so you might want to put the dictionaries you want to modify in your personal documents folder or some other folder where you have write permissions. > > Best regards > Hanno > > Am 09.05.2012 12:40, schrieb Gyorgy SZEIDL: >> dear list members: >> >> i have just installed winedt 7 on a new pc (this is going to be my new >> home computer). >> operating system is windows 7 (64Bit). if i add a new word to my >> hungarian dictionary everything is OK. however when i close the >> program i have an error message: >> >> Error saving dictionary etc. >> >> the same installation works fine on my laptop under windows 7 (32bit). >> i think windows parameters should be changed in order to make possible >> that winedt could save the changes in my hungarian dictionary. >> >> please help, i have no idea what to do. >> >> best regards >> gyorgy >> >> >> >> > > -- > Dr. Hanno Dierke > TU Braunschweig Institut für Produktionsmesstechnik > Schleinitzstr. 20 38106 Braunschweig > Tel. 0531/391-7048 Fax 0531/391-5837 eMail: h.dierke@... >

#11940 From: Philip TAYLOR <P.Taylor@...>
Date: Wed May 9, 2012 1:40 pm
Subject: Re: winedt does not save the changes i have made in a dictionary
P.Taylor@...
Send Email

 McClintock, Peter wrote: > György, > > Probably, if you start WinEdt with a right-click, and then "Run as Administrator", your editing problem will go away. (But Alex considers this to be rather a dubious practice for getting round Windows access problems!) Alex is not alone ! Philip Taylor

#11941 From: "Fox, Gordon" <gfox@...>
Date: Wed May 9, 2012 9:49 pm
Subject: Highlighting R code
gfox@...
Send Email

 I’m writing some R code in WinEDT 7 (build 20120423), using the latest version of R-Sweave. Problem: the highlighting color for comment lines is too dark for me to read the comments – and fiddling in the options interface hasn’t turned up anything for me that changes this. I’m sure I’m missing something simple – can anyone point me in the right direction? Thanks. Gordon --Dr. Gordon A. Fox       Voice: (813)974-7352       Fax: (813)974-3263Dept. of Integrative Biology (SCA 110) (for US mail, but  SCA 112 for couriers)University of South Florida                 4202 E. Fowler Ave.Tampa, FL 33620, USA                   http://foxlab.wordpress.com"Trying is the first step towards failure." -- Homer Simpson

#11942 From: Gyorgy SZEIDL <gyorgy.szeidl@...>
Date: Thu May 10, 2012 6:25 am
Subject: Re: winedt does not save the changes i have made in a dictionary
gyorgy.szeidl@...
Send Email

 Philip, Thank you. You are in all probability right. However I use my home PC as the only user and I do not think that there will be any problem. Thank you for your remark again. Gyorgy > > McClintock, Peter wrote: > >> György, >> >> Probably, if you start WinEdt with a right-click, and then "Run as >> Administrator", your editing problem will go away. (But Alex >> considers this to be rather a dubious practice for getting round >> Windows access problems!) > > Alex is not alone ! > Philip Taylor >

 Messages 11913 - 11942 of 12713   Oldest  |  < Older  |  Newer >  |  Newest

Copyright © 2010 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines NEW - Help