You made it even more clear to me why I think it would not be the best thing to do ;)
but making open on single file trigger project import would be great.
/max
christian
Von: <eclipse.org-architecture-council-bounces@xxxxxxxxxxx<mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx>>
on behalf of Max Rydahl Andersen <manderse@xxxxxxxxxx<mailto:manderse@xxxxxxxxxx>>
Antworten an: "eclipse. org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx<mailto:eclipse.org-architecture-council@xxxxxxxxxxx>>
Datum: Mittwoch, 16. März 2016 um 09:29
An: "eclipse. org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx<mailto:eclipse.org-architecture-council@xxxxxxxxxxx>>
Betreff: Re: [eclipse.org-architecture-council] Eclipse vs Vi vs Sublime
On 16 Mar 2016, at 9:08, Oberhuber, Martin wrote:
Hi,
Ø That would be really slick if it could auto-discover the workspace.
Ø you mean auto-discover .project, right ?
There could be a number of really interesting workflows related to this.
I agree that searching up in the directory hierarchy until a .project is found
(Like git finds the .git folder by searching upwards) is perhaps one of the
most interesting.
Auto-discovering workspaces is also interesting (to keep Preferences) but harder,
since the workspace .metadata Is often located in a completely different folder than the projects.
Eclipse would probably have to globally remember recent workspaces ... something
That reminds me of Oomph Preference Sharing to some extent.
Eclipse does remember recent workspaces.
But I think it will end up being clunky - I think the use of eclipse to open individual files
and have it offer to open "nearest" project if not already open would be a great thing.
This should work from cli but also your favourite file explorer/finder/browser.
/max
Slightly related but in a different direction, I've filed an enhancement request years ago
talking about "workspace description files" (similar to visual studio .dsw):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=245405
Not trying to feature creep here, but I thought you might find this interesting...
Thanks,
Martin
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From:
eclipse.org-architecture-council-bounces@xxxxxxxxxxxeclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxxeclipse.org-architecture-council-bounces@xxxxxxxxxxx]
On Behalf Of Max Rydahl Andersen
Sent: Wednesday, March 16, 2016 8:41 AM
To: eclipse.org-architecture-council
Subject: Re: [eclipse.org-architecture-council] Eclipse vs Vi vs Sublime
Max, thanks for the tip of opening on the command line! It worked on Linux.
Tried with a relative path too ? Thats what failed on me in past with a segfault ;/
That would be really slick if it could auto-discover the workspace.
you mean auto-discover .project, right ?
/max
Jay
On Tue, Mar 15, 2016 at 6:53 PM, Max Rydahl Andersen
manderse@xxxxxxxxxxmanderse@xxxxxxxxxxmanderse@xxxxxxxxxxmanderse@xxxxxxxxxx
wrote:
On 15 Mar 2016, at 18:38, Mickael Istria wrote:
"Quick" editors and IDEs are not competing, they're complementary and
many people use both. IMO, that's perfectly fine.
I disagree. Yes you can use them side-by-side and I do that frequently.
Primarily because the "eclipse myfile.txt" is semi-broken on OSX.
If this was fixed I would use eclipse way more.
/max
http://about.me/maxandersen
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation. To be permanently removed from this list, you must
contact emo@xxxxxxxxxxxemo@xxxxxxxxxxxemo@xxxxxxxxxxxemo@xxxxxxxxxxx to request removal.
--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact
emo@xxxxxxxxxxxemo@xxxxxxxxxxxemo@xxxxxxxxxxxemo@xxxxxxxxxxx to request removal.
/max
http://about.me/maxandersen
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxxeclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact
emo@xxxxxxxxxxxemo@xxxxxxxxxxx to request removal.
/max
http://about.me/maxandersen
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact
emo@xxxxxxxxxxx to request removal.