Legal Opinion

Latimer v. Latimer

Supreme Court of South Carolina

Decided September 17, 1894PublishedCited by 2 opinions

Before Wallace, J., Greenville, November, 1893. This was an action by James H. Latimer against Joseph P. and John EL Latimer, as executors of Hewlett Sullivan, deceased, commenced October 23, 1891. The appeal is from an order of Judge Wallace granting a continuance on the ground that, by order of Judge Izlar of July 11, 1893, under supplementary proceedings in the case of Hewlett Sullivan against P. D. Huff & Co. (James H. Latimer being one of the company), the said James H.…

Read the full summary

Before Wallace, J., Greenville, November, 1893. This was an action by James H. Latimer against Joseph P. and John EL Latimer, as executors of Hewlett Sullivan, deceased, commenced October 23, 1891. The appeal is from an order of Judge Wallace granting a continuance on the ground that, by order of Judge Izlar of July 11, 1893, under supplementary proceedings in the case of Hewlett Sullivan against P. D. Huff & Co. (James H. Latimer being one of the company), the said James H. Latimer had been ordered to assign to the defendants, in this case of Latimer v. Latimer, a portion of the claim here…

1Opinion of the Court

The opinion of the court was delivered by

Mr. Justice Gary.

The action in this case is to recover the sum of $2,250 alleged to be due to the plaintiff by the estate of Hewlett Sullivan, deceased. After the commencement of this action the respondents instituted proeceeding supplementary to the execution against the appellant in the ease of Hewlett Sullivan v. P. D. Huff & Co. These proceedings resulted in an order made by Judge Izlar on the 11th day of July, 1893, by which the appellant was required to pay to the respondents the sum of $1,581.23 within ten days after the service of said order…

2Cited by2 opinions

  1. State v. HunterSupreme Court of South Carolina · 1908
  2. State v. JohnsonSupreme Court of South Carolina · 1912

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API