Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 66085 - [printing][projection] Printing folded regions should print folding markers
Summary: [printing][projection] Printing folded regions should print folding markers
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 66814 88461 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-08 05:38 EDT by Heiko Selber CLA
Modified: 2019-09-04 03:03 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Selber CLA 2004-06-08 05:38:10 EDT 
When I print Java code with folded regions, there is no hint in the printout 
that the region is folded (in Eclipse 3.0M9).

It would be nice if folding were indicated by an ellipsis ("...").

The missing fold markers don't disturb that much when methods are folded, 
because the automatic indentation (if used) shows you that there must be 
something.

If import statements are folded, however, you see only the first one, with no 
hint at all that others are hidden.
Comment 1 Paul Mischler CLA 2004-07-13 10:44:07 EDT 
This is closely related to (if not, a duplicate of) bug 66814?
Comment 2 Dani Megert CLA 2004-07-19 06:28:45 EDT 
*** Bug 66814 has been marked as a duplicate of this bug. ***
Comment 3 Dani Megert CLA 2005-03-21 05:18:04 EST 
*** Bug 88461 has been marked as a duplicate of this bug. ***
Comment 4 Leopold Welsch CLA 2005-09-26 12:14:59 EDT 
Is there any kind of activity for this bug? Considered for 3.2????
Comment 5 Dani Megert CLA 2005-10-03 10:10:27 EDT 
Currently not planned. A patch of good quality is welcome.
Comment 6 Lars Vogel CLA 2019-09-04 03:03:53 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

-