eclipse-texlipse / texlipse

Eclipse Texlipse

Eclipse TeXlipse™

The TeXlipse plugin for Eclipse provides support for LaTeX projects. It is primarily aimed at users who already know the basics about LaTeX, newbies will surely find it useful but also a steeper learning curve. The following main features are offered:

• Syntax highlighting
• Document outline
• Code folding
• Templates
• Build support, also partial building
• Annotations for errors (while editing)
• Content assist (completion of commands and references)
• Easy navigation with F3
• Outline of the current file and the full project
• Spell checking
• Menu with common LaTeX math symbols
• BibTeX editor and BibTeX-support
• BibLaTeX support
• Line wrapping
• Table editor
• Support for several platforms (Windows, Linux, OS X)
• Optional: Live PDF preview with Pdf4Eclipse
• Optional: Bibsonomy integration with TeXlipseBibSonomyExtension
• ...and many more

In other words, TeXlipse includes quite a complete set of features for day-to-day editing tasks. This manual explains the use of these features in detail, but please go ahead and explore TeXlipse!

Getting Started

Setting up a TeXlipse development environment

We are using Eclipse as development IDE and using the latest 2020-20 release as TeXlipse target platform.

Using the TeXlipse development Oomph setup

This approach allows you to start almost from scratch (with JDK 11 (or newer) and a Git client installed already), and to obtain a ready-for-use TeXlipse development environment including :

• an OSGi / Eclipse RCP development environment
• plugins to work with target platform definitions.
• Java code formatting preferences as defined in our Coding Style

This involves following steps :

1. Download and start the Eclipse Installer.
2. Within the wizard switch to advanced mode by selecting it in the burger menu of the upper right corner, then select your desired Eclipse installation package e.g. Eclipse IDE for Eclipse Committers from the product list, set your current Java installation folder as well as 32 Bit or 64 Bit dependent on your Java installation and click next.
3. Select Eclipse Texlipse from the list of projects and click next.
4. Within the Variables window activate Show all variables in the bottom left corner. In the appearing fields, set your desired Installation folder name as well as your Root install folder, click next and confirm the listed execution tasks by pressing the finish button. Let the installer do its thing to download the Eclipse IDE package and extra plugins and to start your new Eclipse instance.
5. When Eclipse is starting, you will see a progress indication at the bottom right for the startup tasks of the Oomph setup for TeXlipse. This will clone the TeXlipse repository.
6. In case your project presentation inside your Project Explorer is set to flat, there should be four projects within your IDE. Open the default.target inside your texlipse project and update the plugins listed there. This will take a while. After it has been updated successfully press Set as Active Target Platform and save the file.
7. To start an Texlipse instance e.g. for testing changes, open the build.properties inside the org.eclipse.texlipse project and press the play button (Launch an Eclipse application) in the upper right corner. A new Eclipse instance will be started, where you can switch to the LaTeX perspective.

Manual setup

Use Eclipse to check out the repository.

1. Install Eclipse IDE for Committers. Other versions may work.
2. Start Eclipse. Create a new workspace. You may need to close the Welcome tab by clicking on the X.
3. Open Window > Show View > Other > Git > Git Repositories
4. Click on Clone a Git repository
5. Click on Clone URI, then Next
6. Enter the URI https://github.com/eclipse/texlipse/
7. In the Branch Selection window, keep the default of the Master branch and click Next.
8. In the Local Destination window, select Finish.

Build your own Eclipse TeXlipse with the TeXlipse development environment

1. Run the texlipse/pom.xml as Maven build by setting the goal to clean install. Within the other projects of the workspace a target folder will be created. In case of an error concerning the org.eclipse.license.feature.group please update the version number provided in the source tab of the default.target.
2. The Maven build creates an update site, which can be used within a fresh Eclipse installation e.g. Eclipse IDE for Eclipse Committers. Open the Install new software site and add the file .../texlipse/org.eclipse.texlipse-site/target/org.eclipse.texlipse-2.0.3.201911021750.zip as new repository.
3. Install the new software LaTeX support for Eclipse. After Eclipse restart you can switch to the LaTeX perspective.

Resources

• The official TeXlipse project page
• The Eclipse Science working group
• Contribution guide

License

EPL v1.0 see LICENSE file.

---

Eclipse TeXlipse, Eclipse, the Eclipse logo, and the Eclipse TeXlipse project logo are either registered trademarks or trademarks of The Eclipse Foundation in the United States and/or other countries.

texlipse's Issues

Configure Mylyn commit message template and issue tracker link

Set up a build job for milestones at the Jenkins CI instance

Editor should recognize labels defined in listings

The TeXlipse editor currently highlights a \ref{} to a label defined within a lstlisting as a missing reference, even though it is present in the document and compiles just fine with the expected result.

Example:

\begin{lstlisting}[caption=My Listing, language=Java, label=mylisting]
System.out.println("Hello world!");
\end{lstlisting}

Listing~\ref{mylisting} shows...

The last line above would have a warning in TeXlipse, claiming that there is no label in the document that matches the reference. This is not only misleading, it can become a real problem when you start ignoring those warnings out of habit, but then your listing unintentionally really went missing in the output document and you end up with a broken reference in the PDF, and you wouldn't notice because the editor behaves "as usual". This only seems to affect labels defined inside listings, regular \label{}s work fine.

Add or link build instructions to README

Please provide build instructions in README.md or a link to them there since the build is more complex than mvn install (see #56).

This can somehow be combined with #24 and #10. They are however not about the specifics of the build process.

Outline not updated after change of document name

Bug report

What is the current behavior?

After changing the name of the master document from document.tex to something more descriptive, both the Outline and the Full LaTeX Outline stopped being updated.

Right after changing the name of the file, clicking on an entry in the Outline would try to open the non-existing file document.tex. After closing and reopening both outlines they would work as expected in jumping into the right file, but at line numbers that are appropriate for the positions in the old file.

What is the expected or desired behavior?

After changing the name of the master document, both outline views should continue to work as normal with the new name of the file.

Please provide steps to reproduce:

• Create a new TeXlipse project, using the default document names.
• Add some structure to you document to make the working of the outline visible
• change the name of the master document file from document.tex to something else.
• change the settings of the TeXlipse configuration to match the name of the new master input file and the name of the output file (so that you get a mydoc.tex-> mydoc.pdf combination)
• edit the structure of the new file by adding more sections/chapters.

Now check the contents of the outlines and try navigating using the elements of the outline tree.

Please describe your environment:

• TeXlipse version: 2.0.2
• Eclipse version: IDE for Java Devs, 2018-09 (4.9.0), Build id: 20180917-1800

Operating system:

• Windows
• macOS
• Linux

Remove --src-specials from xelatex default arguments as it is not supported

https://github.com/eclipse/texlipse/blob/dd800ed5d181fbac75be483935cd063ec7808242/org.eclipse.texlipse/source/org/eclipse/texlipse/builder/XelatexRunner.java#L45

XelatexRunner#getDefaultArguments() inherits the default argument from https://github.com/eclipse/texlipse/blob/dd800ed5d181fbac75be483935cd063ec7808242/org.eclipse.texlipse/source/org/eclipse/texlipse/builder/LatexRunner.java#L63. --src-specials results in following error when running something like xelatex.exe -synctex=1 -interaction=nonstopmode --src-specials index.tex

ERROR xelatex.core - MiKTeX encountered an internal error.
ERROR xelatex.core - Data: 
ERROR xelatex.core - Source: libraries\miktex\texandfriends\include\miktex\texandfriends\StringHandlerImpl.h:47
…
INFO  xelatex - finishing with exit code 1

At least with MikTeX on Windows, guess it is also the case with other distributions.
I googled because I had this issue and found someone else that had the exact same problem https://tex.stackexchange.com/questions/398779/miktex-2-9-internal-error-stringhandlerimpl-h.

Can someone else also confirm that --src-special is problematic? I don’t have enough knowledge to know what it actually means. MikTeX doc says

--src-special
Embed source file information (source specials) in the DVI file.

Does this mean, it should only be passed when generating a dvi but not a pdf?

Automatically detect TeX Live installation on macOS

Bug report

What is the current behavior?

TeX installation is not detected.

What is the expected or desired behavior?

TeX installation is detected.

Please provide steps to reproduce:

Create a new project.

Please describe your environment:

• TeXlipse version: 0.0.0
• Eclipse version: 0.0.0

Operating system:

• Windows
• macOS
• Linux

Display beamer frame titles in latex outline

With latex-beamer, the outline function seems to be largely useless. Most of the time, it is just completely empty for me.

It would be good if it recognizes latex-beamer frames (note that there is \begin{frame} and \frame), and displays frame titles for navigation within the outline. Maybe it would be easier to just treat \frametitle{} as if it were like \paragraph.

In the settings, I can add frame to the list of environments. That works so-and-so. I guess it won't notice any \frame commands; and it does not display frame titles. So you only get a long list that says "frame, frame, frame, frame"...

Install issue with Eclipse Oxygen

I receive this error on Eclipse Oxygen Release Milestone 5 (4.7.0 M5). The plugin won't install.

"An error occurred while installing the items
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]net.sourceforge.texlipse 1.5.0, action=).
Failed to prepare partial IU: [R]net.sourceforge.texlipse 1.5.0."

Enable refactoring of labels

It would be a great improvement if labels (e.g., for figures, tables, sections) could be refactored such that any references to a changing label are updated automatically.

Obtain ownership of the TeXlipse Eclipse Marketplace entry

It would be better if there were not two TeXlipse entries in the marketplace so the Eclipse TeXlipse team would like to obtain ownership of the current entry at https://marketplace.eclipse.org/content/texlipse

Change default shortcuts for comment/uncomment to M1+7 (Ctrl+7)

Default shortcut for commenting lines is now Ctrl+5 and uncomment Esc, Ctrl+5. Default Eclipse shortcut everywhere else is Ctrl+7. Ctrl+7 in a TeX file does not seem to be doing anything else, so changing to Ctrl+7 does not seem to create a conflict with something.

Not sure if that would be easy, but having the same shortcut for a toggle comment function would be cool, also like everywhere else in Eclipse.

Btw: I will finally try to commit something here in around January, have too much else to do right now. I really really like Texlipse, use it a lot and would love to help or implement something real quick and not only report issues.

Glossaries are not built

Bug report

What is the current behavior?

TeXlipse seems to not build Glossaries properly since the last Eclipse 2018-08 update. It seems that no Glassary files are created by makeindex. It worked before I updated my Eclipse platform.

However, acronyms are still displayed correctly, but no list of acronyms is created.

Error: Description Resource Path Location Type
name{glo:XX} has been referenced but does not exist, replaced by a fixed one . Unknown Texlipse Build Error

• TeXlipse version: 2.0.2.201807241928
• Eclipse version: 4.9.0.v20180906-1121

OS: Windows

---

Add a README

Add the TeXlipse configuration to the official list of projects for Eclipse Installer

Change default builder

Currently the default builder is Latex and builders have to be changed individually for each project. Please add an option to set a default builder (e.g., pdflatex)

A fast and reliable build system for latex could be easy

The problem

I am currently using the texlipse 1.5. I have not looked into the texlipse build code yet, but from my experience it seems to follow the traditional aproach: recompile as long as there are undefined references or undefined citation keys in the error log or a limit is reached.

This may be better than the static "compile twice" approach, but still there are some problems:

• it may not notice a change in page numbers. The table of contents lags behind.
• it makes compilation terribly slow if there is an error in the TeX code. (a forgotten \end or a misspelled reference)
• it makes compilation terribly slow if the user makes a reference to a label in another file and saves the file with the reference before saving the file with the label.

A better build system

Some years ago I used a different approach for my own documents that I would love to see implemented in a way that can be used by all latex-authors. My build system was based on GNU make. The idea follows the same principles as a Makefile for c code: generate dependencies and rebuild every file that is older than any of its input files. A latex file will be rebuilt until all the page numbers / references / bookmarks have reached a stable value. It will not be built more often than necessary.

Here is how I addressed some of the tex specific problems that occur in this approach:

Replace timestamps with checksums

There is a cyclic dependency on auxiliary files like .aux, .toc, .out, .bbl. To generate these files we take these files as input. Therefore we cannot use a timestamp to check for a change. I used a checksum, saved the checksum in a file and updated the checksum file only when the checksum changed. This way I had timestamp of the last change of the auxiliary files.

Analyse dependencies

In my system I just parsed the .tex files for \input, \include and \includegraphics. This worked for me, but more general system should not fail just because someone defines \myinput. Instead you should parse the tex console output for the names of input files and also for input files that yet don't exist (No file example.aux).

What can go wrong?

• The system clearly fails if someone outputs a precise time stamp or compilation counter in an auxiliary file. The maximum number of compilations would always be reached. (Some builder configuration options could help)
• In rare cases the output will not settle because of some oscillation cycles. E.g. with varioref: \vref inserts more text when the label is on the next page than when it appears two pages later. Therefore the long text may push the label a page further, leading to a shorter text and the label pulled back again. This should be reported to the user because the reference will never be correct! (This is not a drawback of the build system, but it will detect a wrong reference that would exist anyway)
• It may be a nice feature if the build system automatically tries to delete auxiliary files that produce errors after a change in the .tex file.
• Sometimes the user may want to have a quick compilation rather than correct page numbers. There should be a draft mode to compile only once.

Conclusio

Since there is active development on texlipse now, I hope that the developers consider my suggestions for a new build system.

Set up Tycho building

Add contributor guide

LanguageTool integration

We started working on this during my @vogellacompany copy editor times and I would like to see this integrated into TeXclipse. See also auguster/languagetool-eclipse-plugin#1 (comment) and https://github.com/vogellacompany/languagetool-eclipse-plugin which is the current active upstream. What needs to be done or has @vogella already solved everything?

Create @2x and @1.5x versions of icons, also convert from GIF to PNG

I've already created all the required icons here https://github.com/turesheim/eclipse-equationwriter

Update the user guide

Update link in EclipseTeXlipse.setup to fr.obeo.releng.targetplatform

Bug report

It is no longer available at the specified address and I believe it is now an Eclipse project.

Unable to make Texlipse run biber during build

Feature Request

This is probably more a feature request than a bug report. I use biblatex with backend biber in my file. However, Texlipse does not run biber automatically. I know that probably I can set up a builder to let it do that, however I am unaware of how to do it. The documentation of the old project tells me to set up a builder for biber, but does not explain how. The documentation linked in Eclipse only tells me to use bibtex, which is not recommended anymore (better use biblatex, especially if you deal with other languages than english).

#60 sounds like usually it should work out of the box, so maybe it´s a bug after all. Let me know if you need some more information or if I can help in any way (e.g. by updating the documentation after I got explained how to do it).

What is the current behavior?

Texlipse does not run biber automatically. No documentation available for how let it run biber.

What is the expected or desired behavior?

Either Texlipse detecting automatically if biber is needed to be run, or documentation for builder setup to include biber.

Please provide use cases for changing the current behavior:

Everybody using biblatex with backend biber, which is the recommended bibliography setup in Latex for most usecases.

Other relevant information:

I am on Windows 10, Eclipse 4.10.0, Texlipse 2.0.2.

Thank you for taking over this project, it is by far my favourite Latex Editor!

Installation note

• Why part of project is on sourceforge.net
• The installation note is outdated and shall be revised
• During installation eclipse warn part of files are installed unsigned!!!
• No help, readme or wiki on github
  More on my today note:
• The user manual is outdated (http://texlipse.sourceforge.net/manual/)
• Today normal output is pdf not dvi
• Lets install source from github or Eclipse marketplace
  This is a good project, why don't you maintain it more professionally?
  Please update, now it is an approved Eclipse project and many users are eagerly waiting to see a great tool out of the box, at least for basic application of TeX preparation.

Provide properties pages with resource selection dialogs

The LaTeX properties page requires users to manually type in the names of certain files or folders. This is really cumbersome because users need to memorize the precise names before opening the properties. Instead, provide some mechanism to choose between existing resources below the project root. Possible solutions are summarized here: https://wiki.eclipse.org/FAQ_How_do_I_prompt_the_user_to_select_a_resource%3F

Prepare for initial contribution

See https://www.eclipse.org/projects/handbook/#ip-initial-contribution

Facilitate creation of new projects from existing resources

TeXlipse is not really helpful when it comes to creating a new project on top of existing LaTeX resources (e.g, inside a Git repository).

The wizard for new projects allows to create the project at an external location, which is helpful. But afterwards, there seems no way to select any existing resources from that location, e.g., to serve as the main *.tex file. Instead, all resource names need to be specified manually.

Providing the wizard with dialogs for resource selection would be really helpful. Regarding this, the issue seems highly related to #33.

Cannot connect to evince PDF viewer

I am sorry if this is not the place to state this, but I just cannot make evince pdf viewer work with Eclipse Oxygen (Linux). When I run the preview it says:

running: /usr/bin/evince "/home/ssardina/git/papers/17-HRPlanning.git/main-hrfp-ijcai18.pdf"
viewer> Failed to connect to Mir: Failed to connect to server socket: No such file or directory
viewer> Unable to init server: Could not connect: Connection refused
viewer> Cannot parse arguments: Cannot open display:

is there any place where the instructions to connect PDF viewers are given?

Thanks, so glad this project was revived! :-)

Set up a build job for releases at the Jenkins CI instance

Texlipse preferences crash in Eclipse Photon Release (4.8.0)

Bug report

What is the current behavior?

Opening
Preferences > Texlipse > Builder Settings
as well as
Preferences > Texlipse > Viewer Settings
result in a popup message:
"The currently displayed page contains invalid values"

Configuring texlipse is thus not possible.

What is the expected or desired behavior?

Preferences should be displayed in wich it is possible to set paths to latex / viewer commands

Please provide steps to reproduce:

• Install Eclipse Photon Release (4.8.0)
• Install texlipse 2.0.1 from Eclipse Marketplace
• Restart Eclipse as required
• Open Preferences > Texlipse > Builder Settings

Please describe your environment:

• TeXlipse version: 2.0.1
• Eclipse version: 4.8.0

Operating system:

• Windows
• macOS
• Linux

Further details:
The problem is probably caused by the crash:

Exception:java.lang.NoClassDefFoundError: org/eclipse/ui/help/WorkbenchHelp
	 at org.eclipse.texlipse.properties.ViewerSettingsPreferencePage.createFieldEditors(ViewerSettingsPreferencePage.java:52)
...

and

Exception:java.lang.NoClassDefFoundError: org/eclipse/ui/help/WorkbenchHelp
	 at org.eclipse.texlipse.properties.BuilderSettingsPreferencePage.addBuilderList(BuilderSettingsPreferencePage.java:185)

The likely reason is the removal of deprecated APIs from Eclipse 4.8.0.

Feature branding has some errors

Create a logo for the project

I think the project should have a logo, something easily recognisable. Using LaTeX we can simply use \TeX{lipse} and the image could be something like this:

escaped % signs inside command arguments gray out the line (like for comments)

I have the following

\newcommand{\code}[1]
	{\texttt{#1}}
\code{10 \% (9 \% 6)} 

Everything after % is colored in light grey (default color for comments). However, writing 10 \% (9 \% 6) does not have this problem.
Escaped % signs should not be recognized as comments inside command arguments. This is a bug.

Replace Jazzy with Eclipse's built-in spell checker

Jazzy has not been updated since 2005 and Eclipse has it's own spell checker. It would probably be wiser to go for the one that is being maintained.

Uncommenting of lines that have been commented out

Using Ctrl+5, TeXlipse already supports commenting out the selected lines by prepending a %. However, for lines that have already been commented out, Ctrl+F5 will add another %. Instead, similar to what JDT does for Java, pressing Ctrl+F5 should uncomment a line if it is already commented out.

Invisible labels with cursor on

This bug reports to TeXlipse 1.5.0 on Eclipse 4.7.1a. When the cursor is on a label, be it a \label or \ref block, all its instances become invisible. Here is an example:

Switch license to EPL 2.0

Change default output format from DVI to PDF

Add issue report template

In order to make it easier for issue reporters to describe reproducible issues, we need a template to help ensure all important details are recorded.

Insert the correct quote characters in listings

In standard LaTeX code, it is nice that the TeXlipse editor automatically replaces the double-quote symbol (") with the appropriate LaTeX quotes (``''). However, this is rather annoying when embedding a piece of source code in a listing, because there you actually want the usual quotes. It would be nice if the editor would recognize that the cursor is within a listing context and the quote replacement feature is temporarily disabled for these cases.

Equation editor color bug

Bug report

I still do not know if it's a problem with Eclipse or TeXlipse.
In JAVA I did not notice any problems, but in LaTeX, the equations seem strange, in some places it seems that it was not recognized as an equation, in others it seems normal, as it is in the figure below

What is the current behavior?

Please describe your environment:

This occurs on two different computers with me, one with Windows 10 and another with Ubuntu 18.04.1 LTS, this is the two are with the same Eclipse and TeXlipse
It is the same project that is in GitHub and the errors occur in the same place of the text.

• TeXlipse version: 2.0.2
• Eclipse version: 2018-09 (4.9.0)
  Build id: 20180917-1800

Operating system:

• Windows
• macOS
• Linux

---

Best regards

Protect "master" branch from commits

We should not allow anyone to commit directly to the master branch. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=513311

Provide an Oomph configuration to making it easier for contributors

Set up continuous building with Jenkins-CI

This should probably be deferred until we get the Science TLP key.

Docker-based LaTeX compilation

Feature Request

We are only able to compile documents using pdflatex installed in the host machine.

What is the expected or desired behavior?

The ability to compile documents using pdflatex on a docker guest machine.

Please provide use cases for changing the current behavior:

It could be achieved including docker commands in Builder Settings, such as:

docker run -d -it -v /host/path:/root/shared/folder --name pdflatex-image pdflatex

Other relevant information:

Example of LaTeX in Docker: https://github.com/theredfish/docker-pdflatex

biblatex broken if put in non-main tex file

Bug report

Currently, if the \addbibresource command is used in a different .tex file input e.g. via \input{tex/biblatex}, it is not recognised by Texlipse, so that I only get something along the lines of

lualatex.exe> Package biblatex Warning: Please (re)run Biber on the file:
lualatex.exe> (biblatex)                document
lualatex.exe> (biblatex)                and rerun LaTeX afterwards.

This practically breaks modularization of bigger projects, where I want to explicitly avoid having single package commands in the main tex file.

What is the current behavior?

Texlipse seems not to find \addbibresource if issued in a different than the main .tex file

What is the expected or desired behavior?

Either allow for \addbibresource in tex files input via \input{}, or allow more explicit selection of build steps.

Please provide steps to reproduce:

document.tex:

\documentclass{article}
\input{biblatex}
\begin{document}
\section{Title}
\subsection{Subtitle}
Plain text.
\subsection{Another subtitle}
More plain text. \cite{0029-5515-57-10-102020}
\printbibliography
\end{document}

biblatex.tex:

\usepackage[backref=true,backend=biber]{biblatex}
\addbibresource{bibliography/bibliography.bib}

bibliography/bibliography.bib:

@Article{0029-5515-57-10-102020,
  author       = {Wolf, R. C. and others},
  title        = {Major results from the first plasma campaign of the Wendelstein 7-X stellarator},
  journaltitle = {Nuclear Fusion},
  date         = {2017-07-27},
  volume       = {57},
  number       = {10},
  pages        = {102020},
  doi          = {10.1088/1741-4326/aa770d},
}

Adding \addbibresource{bibliography/bibliography.bib} to document.tex makes it work.

Please describe your environment:

• TeXlipse version: 2.0.1.201801202105
• Eclipse version: Oxygen.3a Release (4.7.3a), Build id: 20180405-1200

Operating system:

• Windows 10

---

Synchronisation between TeXlipse editor and external viewer does not work

At least I believe, I have minimal knowledge about native methods. I write down how I discovered that, so maybe someone can point out that this error is something completely different and can give me a solution :D
I have been using this tutorial for years to configure inverse search support for SumatraPDF. With the 2.0.0 release it’s not working anymore.

I send the command javaw -classpath [...]\.p2\pool\plugins\org.eclipse.texlipse_2.0.0.201709271122.jar" org.eclipse.texlipse.viewer.util.FileLocationClient -p 55000 -f %f -l %l from Sumatra when double clicking to start the inverse search and have the focus set to Eclipse and jump to the line that defines the double clicked text. Inverse search support port number is left at its default 55000.
Whenever I double click and the command is sent, Eclipse shows an error dialog and the error log shows An internal error occurred during: "Launching Preview Document in sumatra PDF". with the stacktrace.

java.lang.UnsatisfiedLinkError: org.eclipse.texlipse.DDEClient.execute(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)I
	at org.eclipse.texlipse.DDEClient.execute(Native Method)
	at org.eclipse.texlipse.viewer.ViewerManager.sendDDEViewCommand(ViewerManager.java:392)
	at org.eclipse.texlipse.viewer.ViewerManager.preview(ViewerManager.java:147)
	at org.eclipse.texlipse.viewer.TexLaunchConfigurationDelegate.launch(TexLaunchConfigurationDelegate.java:68)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

So I looked at DDEClient.execute, saw what library it was loading (I have a 64bit Win10 and System.getProperty("os.arch") returns amd64 so ddeclient-x86_64 is loaded. I thought maybe the DLL cannot be loaded so I moved it to a folder that is included in my PATH variable but that resulted in the same error.
Then I examined the DLL with a tool that shows the exported functions and found that the function is still named with the old package naming net.sourceforge.texlipse.

I guess that’s the problem, right? If not, I would love to have a hint. Until then I’m going back to the 1.5.0 release with net.sourceforge.texlipse package naming because I cannot work productively without this feature.

Oh, and don’t forget to also rename the 32 Bit DLL function name :)

Reorganise into one Eclipse plug-in and one feature bundle

Word wrapping issues

Bug report

What is the current behavior?

Word wrapping does not function when working on a file after starting eclipse.

What is the expected or desired behavior?

Word wrapping should wrap text if enabled.

Please provide steps to reproduce, including full log output:

N/A (?)

Please describe your environment:

• TeXlipse version: 2.0.0
• Eclipse version: 4.7.2
• Operating system:

• Windows
• macOS
• Linux

Edited original to fit issue template. Original below:

I am currently using the 2.0.0 release having switched from a custom 1.5.0 build.

Word wrapping was never working 100% in any release. I have never used soft wrapping (still says "experimental" in the UI).

A long standing issue was word wrapping when using tabs. Tabs at the beginning of a line would never cause wraps until much later than the margin. A workaround to this was to use spaces to make sure the lines wrapped at the correct point.

Current issue is wrapping in general. Wrapping text does not work when starting eclipse. Only after disabling and enabling wrapping does the text begin to wrap again.

Long time texlipse user. I will be posting a few issues over the next few weeks.