Hi all

 

Has anyone else experienced this?

 

I’m compiling a document in WinEdt 7, and press Ctrl-Alt-X to run TeXify.

 

After pressing Ctrl-Alt-x and compilation finishes, a letter “x” is inserted where the cursor is located, i.e. the “x” is buffered and “placed” in the document when in fact it ought to have been a shortcut key.

 

Thanks

 

Hubert

I have installed Winedt 7 on Windows 7 using standard options. I need
to change some settings in the Execution modes dialog box, but this
option is grayed out and I cannot open it. I am wondering what is
wrong with my settings.

Thanks,

Per

Il 01/05/2012 22.48, Per Ting ha scritto:
> I have installed Winedt 7 on Windows 7 using standard options. I need
> to change some settings in the Execution modes dialog box, but this
> option is grayed out and I cannot open it. I am wondering what is
> wrong with my settings.
>
> Thanks,
>
> Per
>

Did you installed over a previous build without following the upgrading
procedure?

Karl

Maarten,

This one will turn out to have nothing to do with WinEdt.

> I'm having problems with forward search for PDF documents with
> Winedt 7. It not working, either in Adobe reader, Adobe Acrobat
> Pro or Sumatra PDF. With the latter, I get the error message
> "Unknown source file...". If I compile to DVI and use Yap, forward
> search works fine.
>
> I'm using Win7 64bit with MikTex 2.9.

For educational purposes:

You cannot compare dvi search with pdf search: the former one uses
SRC specials embedded by TeX in dvi file and the later one uses
supplementary sync information produced by TeX in .synctex file.

In the case of Adobe, WinEdt's own synctex parsing algorithm
cannot find any reference to the file from which you are
initiating the search in .synctex file. However, Sumatra PDF has
its own algorithm to parse synctex files and it, too, cannot
locate the source file from the available data in .synctex file.
So probably there is something wrong with it (remember it is
produced by TeX and not WinEdt).

Does the Inverse Search from Sumatra work?

Try:

0. Delete synctex file and recompile to generate a new one. Still
a problem?

1. Open one of WinEdt's LaTeX Samples (Documents Menu) and see if
it works with this one.

2. You can open your .synctex file in WinEdt (also check the date
on it) and then search for the name of the file from which you are
initiating the search. It should be somewhere there in semi-raw
text data. See if there is something odd there...

     ... and avoid spaces and international characters in filenames.
     WinEdt has no problem with them but TeX often does.

That's just about all I can advise you (it is really not a WinEdt
issue)...

Best regards,

alex

Hi again all,

Why was the Alt-Enter shortcut key removed? Would there be any possibility in
restoring it (either in a later build or by myself in some way?)

Whilst solutions have been offered, I'm still finding Alt-Enter to be easier :p

Thanks

Hubert
________________________________________
From: Karl Koeller [karlkoeller@...]
Sent: Wednesday, 21 March 2012 7:14 AM
To: winedt+list@...
Subject: Re: [WinEdt] ANN: WinEdt 7 - minor bug

Il 20/03/2012 21.08, Hubert Lam ha scritto:
> Hi Alex/all
>
> Just wondering if anyone else has installed WinEdt 7 but has lost the ability
to press Alt-Enter to "complete" the "\end{" statement?
>
> In WinEdt 5/6 I used to be able to type "\begin{enumerate}", hit Alt-Enter and
it would autocomplete the "\end{enumerate}" for me. The only thing that works
now (which also worked before) is to type in "\begin{enumerate}" and type in
"\end{{" in order to have the autocomplete function.
>
> Having said that, it seems to be a far faster release -- WinEdt 6 could be
quite slow in opening multiple files (for a project).
>
> Thanks
>
> Hubert
> ________________________________________
> From: WinEdt Team [support@...]
> Sent: Wednesday, 21 March 2012 12:38 AM
> To: winedt+list@...
> Subject: Re: [WinEdt] ANN: WinEdt 7 - minor bug
>
>> I just installed WinEdt 7 on my Windows 7.
>>
>

Just type


\begin{enumerate}>

On 5/1/2012 5:01 PM, Karl Koeller wrote:
> Il 01/05/2012 22.48, Per Ting ha scritto:
>> I have installed Winedt 7 on Windows 7 using standard options. I need
>> to change some settings in the Execution modes dialog box, but this
>> option is grayed out and I cannot open it. I am wondering what is
>> wrong with my settings.
>>
>> Thanks,
>>
>> Per
>>
>
> Did you installed over a previous build without following the
> upgrading procedure?
>
> Karl
>

I do not recall, but it is possible. I do not have this problem on my
other machine, probably I have done the upgrading correctly there.

Per

Il 01/05/2012 23.48, Hubert Lam ha scritto:
> Hi again all,
>
> Why was the Alt-Enter shortcut key removed? Would there be any possibility in
restoring it (either in a later build or by myself in some way?)
>
> Whilst solutions have been offered, I'm still finding Alt-Enter to be easier
:p
>
> Thanks
>
> Hubert
> ________________________________________

I already said in this list that Alt+Enter is now used for Abbreviation.
The shortcut for Active String (the one you're looking for) is now
Shift+Alt+Enter.

If you want to swap them, in MainMenu.ini search for

    ITEM="Abbreviation"

and substitute the related shortcut with

    SHORTCUT="40973::Shift+Alt+Enter"

Then search for

    ITEM="Activate"

and substitute the related shortcut with

    SHORTCUT="32781::Alt+Enter"

Remember to load the script...

Karl

Il 02/05/2012 0.24, Per Ting ha scritto:
> I do not recall, but it is possible. I do not have this problem on my
> other machine, probably I have done the upgrading correctly there.
>
> Per

In this case, execute the following commands from Options menu, in this
order:

1) Maintenance -> Rebuild Default
2) Configurations -> Default
3) Maintenance -> Upgrade Personal Configuration

Note that you may have lost your custom Execution Modes settings.

Karl

Thanks for the info, Alex.

Deleting the synctex file didn't help, and also for the WinEdt sample
files the problem persisted. I also couldn't find anything wrong with
the synctex file.

But after a re-install, forward search is now working for Sumatra for
some reason. It's not yet working for Adobe, but it's good enough for me.

Thanks & cheers,
Maarten

On 01-May-12 11:34 PM, WinEdt Team wrote:
> Maarten,
>
> This one will turn out to have nothing to do with WinEdt.
>
>> I'm having problems with forward search for PDF documents with
>> Winedt 7. It not working, either in Adobe reader, Adobe Acrobat
>> Pro or Sumatra PDF. With the latter, I get the error message
>> "Unknown source file...". If I compile to DVI and use Yap, forward
>> search works fine.
>>
>> I'm using Win7 64bit with MikTex 2.9.
>
> For educational purposes:
>
> You cannot compare dvi search with pdf search: the former one uses
> SRC specials embedded by TeX in dvi file and the later one uses
> supplementary sync information produced by TeX in .synctex file.
>
> In the case of Adobe, WinEdt's own synctex parsing algorithm
> cannot find any reference to the file from which you are
> initiating the search in .synctex file. However, Sumatra PDF has
> its own algorithm to parse synctex files and it, too, cannot
> locate the source file from the available data in .synctex file.
> So probably there is something wrong with it (remember it is
> produced by TeX and not WinEdt).
>
> Does the Inverse Search from Sumatra work?
>
> Try:
>
> 0. Delete synctex file and recompile to generate a new one. Still
> a problem?
>
> 1. Open one of WinEdt's LaTeX Samples (Documents Menu) and see if
> it works with this one.
>
> 2. You can open your .synctex file in WinEdt (also check the date
> on it) and then search for the name of the file from which you are
> initiating the search. It should be somewhere there in semi-raw
> text data. See if there is something odd there...
>
>    ... and avoid spaces and international characters in filenames.
>    WinEdt has no problem with them but TeX often does.
>
> That's just about all I can advise you (it is really not a WinEdt
> issue)...
>
> Best regards,
>
> alex
>

--
PhD student
Biogeochemical Model-Data Integration Group, Max Planck Institute for
Biogeochemistry
Earth System Science and Climate Change Group, Wageningen University

Contact details:
Max-Planck-Institute for Biogeochemistry
Hans-Knöll-Str. 10
D-07745 Jena Germany
Office: C1.010
phone: +49 3641 576266
fax: +49 3641 577200
WWW: http://www.bgc-jena.mpg.de/bgc-mdi/

On 2012. 05. 01. 23:01, Karl Koeller wrote:
> Il 01/05/2012 22.48, Per Ting ha scritto:
>> I have installed Winedt 7 on Windows 7 using standard options. I need
>> to change some settings in the Execution modes dialog box, but this
>> option is grayed out and I cannot open it. I am wondering what is
>> wrong with my settings.
>>
>> Thanks,
>>
>> Per
>>
>
> Did you installed over a previous build without following the
> upgrading procedure?
>
> Karl
>
dear karl:

i am facing with the same problem:

I purchased a new computer as my office computer last friday
-- windows 7 (64bit) . i have installed winedt  2012-04-23 (a brand
new installation)  today. i reconfigured it by uploading my own settings.
when i wanted to adjust the page size to a4 for pdftexify i was
surprised to see that the line execution modes is grey, i.e., it is
unavailable. what have i done wrong?
thank you for your help in advance.
best regards
gyorgy

Il 02/05/2012 14.35, Gyorgy SZEIDL ha scritto:
>
> dear karl:
>
> i am facing with the same problem:
>
> I purchased a new computer as my office computer last friday
> -- windows 7 (64bit) . i have installed winedt  2012-04-23 (a brand
> new installation)  today. i reconfigured it by uploading my own settings.
> when i wanted to adjust the page size to a4 for pdftexify i was
> surprised to see that the line execution modes is grey, i.e., it is
> unavailable. what have i done wrong?
> thank you for your help in advance.
> best regards
> gyorgy
>

I repeat for the umpteenth time (your saved settings are from a previous
build so you have to upgrade):

execute the following commands from Options menu, in this order:

1) Maintenance -> Rebuild Default
2) Configurations -> Default
3) Maintenance -> Upgrade Personal Configuration


Karl

On 5/2/2012 2:45 PM, Karl Koeller wrote:
> Il 02/05/2012 14.35, Gyorgy SZEIDL ha scritto:
>>
>> dear karl:
>>
>> i am facing with the same problem:
>>
>> I purchased a new computer as my office computer last friday
>> -- windows 7 (64bit) . i have installed winedt  2012-04-23 (a brand
>> new installation)  today. i reconfigured it by uploading my own
>> settings.
>> when i wanted to adjust the page size to a4 for pdftexify i was
>> surprised to see that the line execution modes is grey, i.e., it is
>> unavailable. what have i done wrong?
>> thank you for your help in advance.
>> best regards
>> gyorgy
>>
>
> I repeat for the umpteenth time (your saved settings are from a
> previous build so you have to upgrade):
>
> execute the following commands from Options menu, in this order:
>
> 1) Maintenance -> Rebuild Default
> 2) Configurations -> Default
> 3) Maintenance -> Upgrade Personal Configuration
>
>
> Karl
>
>
dear karl:
thank you very much. it has worked perfectly.
best regards
gyorgy

I have updated from winedt5 to winedt7. I'm totally lost in configuration of
winedt

I'd like to know how to configure the traslate table, since when I type
directly  the letters with accent in winedt, it's bizarre character at
output, i have to type \'e  in place of é for example. I have enabled
tex_read and tex_write in translate table.ini

Thak you very much
Tao JIANG

Am Thu, 3 May 2012 13:06:08 +0200 schrieb Tao JIANG:

> I have updated from winedt5 to winedt7. I'm totally lost in configuration of
> winedt
>
> I'd like to know how to configure the traslate table, since when I type
> directly  the letters with accent in winedt, it's bizarre character at
> output, i have to type \'e  in place of é for example. I have enabled
> tex_read and tex_write in translate table.ini

If you are using LaTeX there is no need to enable translation
tables. Use \usepackage[utf8]{inputenc} or
\usepackage[ansinew]{inputenc} depending on the encoding of your
.tex file.


--
Ulrike Fischer

Thank you very much. It's OK now!
Tao
----- Original Message -----
From: "Ulrike Fischer" <list@...>
To: <winedt+list@...>
Sent: Thursday, May 03, 2012 1:53 PM
Subject: [WinEdt] Re: Winedt 7: How to suppress a confirmation dialog


> Am Thu, 3 May 2012 13:06:08 +0200 schrieb Tao JIANG:
>
>> I have updated from winedt5 to winedt7. I'm totally lost in configuration
>> of
>> winedt
>>
>> I'd like to know how to configure the traslate table, since when I type
>> directly  the letters with accent in winedt, it's bizarre character at
>> output, i have to type \'e  in place of é for example. I have enabled
>> tex_read and tex_write in translate table.ini
>
> If you are using LaTeX there is no need to enable translation
> tables. Use \usepackage[utf8]{inputenc} or
> \usepackage[ansinew]{inputenc} depending on the encoding of your
> .tex file.
>
>
> --
> Ulrike Fischer
>

I would still like to know how to change the winedt configuration to run my
ancient files which had [latin1]{inputenc} as input encoding, now with
winedt 7 this commande translate incorrectly the letters with accent and my
é û..   I have to change each file using utf8 as inputenc option.

Thank you for your attention
tao

----- Original Message -----
From: "Ulrike Fischer" <list@...>
To: <winedt+list@...>
Sent: Thursday, May 03, 2012 1:53 PM
Subject: [WinEdt] Re: Winedt 7: How to suppress a confirmation dialog


> Am Thu, 3 May 2012 13:06:08 +0200 schrieb Tao JIANG:
>
>> I have updated from winedt5 to winedt7. I'm totally lost in configuration
>> of
>> winedt
>>
>> I'd like to know how to configure the traslate table, since when I type
>> directly  the letters with accent in winedt, it's bizarre character at
>> output, i have to type \'e  in place of é for example. I have enabled
>> tex_read and tex_write in translate table.ini
>
> If you are using LaTeX there is no need to enable translation
> tables. Use \usepackage[utf8]{inputenc} or
> \usepackage[ansinew]{inputenc} depending on the encoding of your
> .tex file.
>
>
> --
> Ulrike Fischer
>

Am Fri, 4 May 2012 08:43:20 +0200 schrieb Tao JIANG:

> I would still like to know how to change the winedt configuration to run my
> ancient files which had [latin1]{inputenc} as input encoding, now with
> winedt 7 this commande translate incorrectly the letters with accent and my
> é û..   I have to change each file using utf8 as inputenc option.

Winedt doesn't change the encoding of existing files. If [latin1]
worked previously it should work now too -- unless you are
reencoding the file somehow. Check the encoding of the files in the
document settings.


--
Ulrike Fischer

Thank you very much for your answer. It seems that I have understood a
little more. My ancient file is also in ansi, but with translated activited,
so open with translate desactivated, it shows  \'{e} instead of é.

Also, my problèm seems rather latex one, since  with beamer class i can use
latin1 inputenc while with article class the letter is omitted.

Thank you again.
Tao
----- Original Message -----
From: "Ulrike Fischer" <list@...>
To: <winedt+list@...>
Sent: Friday, May 04, 2012 9:44 AM
Subject: [WinEdt] Re: configuration winedt


> Am Fri, 4 May 2012 08:43:20 +0200 schrieb Tao JIANG:
>
>> I would still like to know how to change the winedt configuration to run
>> my
>> ancient files which had [latin1]{inputenc} as input encoding, now with
>> winedt 7 this commande translate incorrectly the letters with accent and
>> my
>> é û..   I have to change each file using utf8 as inputenc option.
>
> Winedt doesn't change the encoding of existing files. If [latin1]
> worked previously it should work now too -- unless you are
> reencoding the file somehow. Check the encoding of the files in the
> document settings.
>
>
> --
> Ulrike Fischer
>

I'm sorry, it was not the problem of latex,but real a problem of encoding. I
don't know when i have switched to utf-8, thus with latin1, it doesn't work.
Thank you again for several exchanges with you, that make me to take into
consideration the problem of document encoding that i have never  worried
about.
Tao



----- Original Message -----
From: "Ulrike Fischer" <list@...>
To: <winedt+list@...>
Sent: Friday, May 04, 2012 9:44 AM
Subject: [WinEdt] Re: configuration winedt


> Am Fri, 4 May 2012 08:43:20 +0200 schrieb Tao JIANG:
>
>> I would still like to know how to change the winedt configuration to run
>> my
>> ancient files which had [latin1]{inputenc} as input encoding, now with
>> winedt 7 this commande translate incorrectly the letters with accent and
>> my
>> é û..   I have to change each file using utf8 as inputenc option.
>
> Winedt doesn't change the encoding of existing files. If [latin1]
> worked previously it should work now too -- unless you are
> reencoding the file somehow. Check the encoding of the files in the
> document settings.
>
>
> --
> Ulrike Fischer
>

I would like my "proper" selection to have a particular background color, say,
BACKGROUND_RGB="$FABD98", but I want my text to have whatever the default text
color is.

In a tex file, for example, I might have

    \subsection{label}

and in WinEdt the default highlighting shows the backslash and braces in red,
"subsection" in blue, and "label" in green.  When I select this text, I want to
have the background shaded but I want the text to retain these same colors.

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?

--
  David
 

Il 04/05/2012 15.56, David Huffer ha scritto:
> I would like my "proper" selection to have a particular background color, say,
BACKGROUND_RGB="$FABD98", but I want my text to have whatever the default text
color is.
>
> In a tex file, for example, I might have
>
>     \subsection{label}
>
> and in WinEdt the default highlighting shows the backslash and braces in red,
"subsection" in blue, and "label" in green.  When I select this text, I want to
have the background shaded but I want the text to retain these same colors.
>
> 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?
>
> --
>   David

Did you have a look at the manual (Configuration manual -> Highlighting
-> Selections) before posting this message?

Probably not...  You could have read that TEXT_COLOR is a 'color index'
specification and following the link you could have read that 'Value -1
indicates the default or inherited color'.

The last means that (if not inherited from somewhere else, as in this
case) the default color is used. 'Default' means Windows default, that
is the color used by Windows for selections, which is white.

In other words, the default Windows color can not be modified by WinEdt.
So, you can choose to have it white or you can specify a non-negative
one, but in any case you can not have it 'WinEdt-highlighted'.

PS: Nothing against you, David, of course. To you and to all those
reading this reply: taking a look at the manual before posting a message
is a good practice and allows you to learn much more about WinEdt.

Karl

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.

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.

Thanks for your response, though.  It certainly makes my decision to invest in
this software an easier one.

--
  David
 
  -----------------------------------------------------
  David Huffer, Ph.D.
  Deputy Director
  CSOSA/ORE
  Washington, DC
  -----------------------------------------------------


----- Original Message -----
From: Karl Koeller <karlkoeller@...>
To: winedt+list@... <winedt+list@...>
Sent: Fri May 04 10:44:22 2012
Subject: Re: [WinEdt] Selection

Il 04/05/2012 15.56, David Huffer ha scritto:
> I would like my "proper" selection to have a particular background color, say,
BACKGROUND_RGB="$FABD98", but I want my text to have whatever the default text
color is.
>
> In a tex file, for example, I might have
>
>     \subsection{label}
>
> and in WinEdt the default highlighting shows the backslash and braces in red,
"subsection" in blue, and "label" in green.  When I select this text, I want to
have the background shaded but I want the text to retain these same colors.
>
> 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?
>
> --
>   David

Did you have a look at the manual (Configuration manual -> Highlighting
-> Selections) before posting this message?

Probably not...  You could have read that TEXT_COLOR is a 'color index'
specification and following the link you could have read that 'Value -1
indicates the default or inherited color'.

The last means that (if not inherited from somewhere else, as in this
case) the default color is used. 'Default' means Windows default, that
is the color used by Windows for selections, which is white.

In other words, the default Windows color can not be modified by WinEdt.
So, you can choose to have it white or you can specify a non-negative
one, but in any case you can not have it 'WinEdt-highlighted'.

PS: Nothing against you, David, of course. To you and to all those
reading this reply: taking a look at the manual before posting a message
is a good practice and allows you to learn much more about WinEdt.

Karl

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.

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

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

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

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

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

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