This is an automated notification sent by Gna!.
It relates to:
bugs #1832, project xtla.el
==============================================================================
LATEST MODIFICATIONS of bugs #1832:
==============================================================================
Posted by: Matthieu MOY <moy>
Posted on: Sat 11/06/2004 at 11:52 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Category | any | xtla.el
Resolution | None | Fixed
Assigned to | None | moy
Status | Open | Closed
Merge available | No | Already merged
merge request | | [EMAIL PROTECTED]
Fixed Release | | [EMAIL PROTECTED]
------------------ Additional Follow-up Comments ----------------------------
OK.
[EMAIL PROTECTED] solves the problem: The return value didn't use the output of
the process, so it was perfectly safe to use tla--run-tla-async.
==============================================================================
OVERVIEW of bugs #1832:
==============================================================================
URL:
<http://gna.org/bugs/?func=detailitem&item_id=1832>
Project: xtla.el
Submitted by: Masatake YAMATO
Submitted on: Fri 11/05/2004 at 15:27
Category: xtla.el
Priority: 1 - Later
Resolution: Fixed
Assigned to: moy
Originator Email:
Status: Closed
Planned Release: 0.9
Type of request: small bug
Merge available: Already merged
merge request: [EMAIL PROTECTED]
Fixed Release: [EMAIL PROTECTED]
Test case in xtla-tests.el:
Summary: Async running of tla-start-project
_______________________________________________________
Original Submission:
'tla import' in tla-start-project is run synchronously.
However, tla-start-project also should return new version name and location.
Both requirement should be satisfied.
See [EMAIL PROTECTED]
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sat 11/06/2004 at 11:52 By: Matthieu MOY <moy>
OK.
[EMAIL PROTECTED] solves the problem: The return value didn't use the output of
the process, so it was perfectly safe to use tla--run-tla-async.
-------------------------------------------------------
Date: Sat 11/06/2004 at 04:04 By: Masatake YAMATO <jet>
The original code used tla--run-tla-async.
However, my patch uses tla--run-tla-sync to return the result.
Is there any strong requirement to use async function?
(I cannot find any advantage about using async function.)
If not, my patch closes this bug.
-------------------------------------------------------
Date: Sat 11/06/2004 at 01:17 By: Matthieu MOY <moy>
I don't understand where the "bug" is.
Your patch seems to do what you describe. Can we close the bug?
Thanks,
Matthieu.
==============================================================================
This item URL is:
<http://gna.org/bugs/?func=detailitem&item_id=1832>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
