Comments (14)
Yes, this would be a useful option for larger documents. It could be
implemented as a Qt "Dock" window (like
the PDF Bookmarks, PDF Info, etc.)
If someone wants to implement such a Dock before I get around to working on it,
feel free. :-) It might well be
possible to reuse code or at least ideas from one of the other environments
such as TeXmaker or Kile.
If anyone looks into this, please beware of user interface clutter; keep it as
clear and simple as possible!
Original comment by [email protected]
on 29 Jul 2008 at 10:04
- Changed state: Accepted
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from texworks.
I've implemented a Tags panel in rev.154; it will appear in the next snapshots.
This
recognizes LaTeX sectioning commands (\part, \chapter, \section, etc); in
addition,
lines beginning with "%:" are treated as tags and added to the panel. Such "tag
comments" are listed separately before the LaTeX sectioning commands, so as not
to
interfere with the outline structure of the sections.
Currently, the patterns are hard-coded; these need to be customizable (e.g, for
ConTeXt rather than LaTeX, etc).
Original comment by [email protected]
on 13 Sep 2008 at 11:17
- Changed state: Started
from texworks.
This is looking great and working nicely, at least in the Mac where I have been
able
to try it.
The \input and \include commands probably need to be recognised as well. This
would
allow you to easily navigate a complete document across files, and click-open
them
directly from the main file.
Actually, what I have seen in other editors and found very handy is to have a
tree
based on a "main" file. This means the document structure tree (aka Tags panel)
stays
as it is no matter which file of a given project or document you have open, thus
allowing you to jump around within the whole set of related files.
Best, with thanks.
Original comment by [email protected]
on 18 Sep 2008 at 11:49
from texworks.
The last entry for a sidebar with sections is from a year ago. Is this feature
still
in development? It would be nice to have
Original comment by [email protected]
on 31 Aug 2009 at 1:01
from texworks.
Which aspects do you have in mind? The principle tags sidebar is part of Tw for
a
long time (as you mentioned). Proper handling of \input and \include is not
likely to
appear until the implementation of project support (including code to properly
handle
numerous files). If you'd like to see other things in this feature, just post
them.
Original comment by st.loeffler
on 6 Sep 2009 at 8:23
from texworks.
Is there a way we could help further the development of code for proper
handling of
numerous files, and thus of \input and \include? I am rather code illiterate,
but if
I can go over some existing code and isolate related lines and pass them to
someone
who knows about it, I would happy to do so. Or if there is a repetitive boring
task
needed in order to develop this, I can volunteer a few hours for slave work.
Cheers
Original comment by [email protected]
on 6 Sep 2009 at 1:01
from texworks.
First of all, thanks for the offer. Unfortunately, there's no way I can think
of to
further the development right now, save of doing it on your own ;). We're
currently
in the process of fixing up loose ends for the release, once that's over we'll
get
back to the development of new features, with project support being on the top
of my
personal list. I'd recommend tuning in on the mailing list to keep up to date
to the
process and find opportunities to help.
Original comment by st.loeffler
on 6 Sep 2009 at 6:01
from texworks.
(r436) The tags pane must be opened explicitly with each new document opened,
and is "forgotten" after a
document is closed again. I understand support for per-file preferences might
not yet exist, but a global
memory of whether the tags pane should be opened or closed would be great.
(Actually, same goes for which toolbars to show, but that doesn't belong in
this issue.)
Original comment by [email protected]
on 30 Sep 2009 at 12:01
from texworks.
I am using TeXWorks 0.3 (rev 514, if this is useful). The tags window does not
show
a section, subsection, etc. when the name of the section is split between two
lines.
For example, the following section would not show in the Tags window:
***
\section{My coauthor use a
dreadful program which cuts lines arbitrarily}
***
And the example tells you why I care :).
Sorry, my coding skills are nil. I cannot help on this.
Original comment by [email protected]
on 14 Jan 2010 at 8:28
from texworks.
This is because the process of scanning for "tags" happens on a line-by-line
basis, and it's looking for a
complete \section{......} command; the explicit line-break means it doesn't see
it.
(There are other things that could confuse it, too - if you have complex markup
including braces *within* the
section heading, then it won't show quite the right thing. This is because it's
not actually parsing or interpreting
the TeX code, which is potentially a very complex process; it's just scanning
for certain simple patterns.)
One thing you could do to improve the behavior for your particular situation
would be to edit the configuration
file tag-patterns.txt (you'll find it within the TeXworks resources folder,
"configuration" subfolder), and change
the line
1 ^\s*\\part\*?\s*(?:\[[^]]*\]\s*)?\{([^}]*)\}
to
1 ^\s*\\part\*?\s*(?:\[[^]]*\]\s*)?\{([^}]*)
(i.e. simply remove the final "\}"). Do the same for each of the sectioning
commands there.
With this change, it will no longer care whether there's a closing brace at the
end of the \section command, and
so in your example you'd at least get an entry that shows "My coauthor use a"
in the Tags panel.
Original comment by [email protected]
on 14 Jan 2010 at 9:23
from texworks.
It works. Thanks.
J.
Original comment by [email protected]
on 14 Jan 2010 at 3:12
from texworks.
Tags window shows tags from the current file only.
It'd be nice to see all tags from a multifile document.
Original comment by [email protected]
on 13 Nov 2010 at 11:39
from texworks.
Agreed. Implementation-wise, this will need a lot more infrastructure, though.
Therefore, this will have to wait for issue 28 (project support).
Original comment by st.loeffler
on 14 Nov 2010 at 9:29
from texworks.
Hey, so it seems this issue has been dead for quite some time.
But still I think it would be a very nice feature to have:
- A list of all tags and bookmarks, including those from other subfiles
- A tree view of the included subfiles
- If the editor would remember globally wether to show the sidepane on startup
or not.
Original comment by [email protected]
on 23 Feb 2015 at 10:07
from texworks.
Related Issues (20)
- More reactive changes in the settings.
- Choose syntax chunk format
- MacOS X: wrong main menu HOT 2
- Lua scripting, arm64 and x86_64 on OSX HOT 2
- .bib file interface HOT 2
- Topmost CMakeLists.txt:
- Version not provided for winget
- Add citation keys from JabRef
- test_UI fails because 112,38 != 112,39 HOT 1
- symbol lookup error HOT 2
- Randomly closes with error after compilation ends HOT 8
- U+2028 LINE SEPARATOR in editor HOT 3
- Editor: unexpected space=no break space HOT 3
- PDF Preview Lines Look Bad / Artifacted in Windows HOT 3
- Go to line dialog
- Enhance the tag panel of the editor
- 'Insert Citations' feature: implementations request
- test_poppler-qt6 (Failed) on Fedora 40 HOT 3
- Ugly rendering of the output visualization of TeXworks HOT 13
- Building texworks on OSX Ventura / Apple Silicon HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from texworks.