Legal Opinion

Western Union Telegraph Co. v. Bright

Supreme Court of Virginia

Decided September 13, 1894PublishedCited by 13 opinions

Argued at Wytheville. Decided at Staunton. Error to judgment of circuit court of Franklin county, rendered October 26, 1892, in a proceeding by motion wherein George M. Bright was plaintiff, and the Western Union Telegraph Company was defendant. The judgment being adverse to the defendant company, it obtained a writ of error from one of the judges of this court. Opinion states the case.

1Opinion of the Court

Lewis, P.,

delivered the opinion of the court.

This was a motion , in the court below to recover a penalty of $100, provided by section 1292 of the Code, for the failure of the defendant company to deliver as promptly as practicable a certain dispatch transmitted from Abingdon to Bocky Mount (points within this State), and addressed to the plaintiff. ' Section 8211, under which the proceeding was bad, enacts that “ any person, entitled to recover money by action under a contract, may, on motion before any court which would have jurisdiction in an action, otherwise than under section 8215,…

2Cases cited6 opinions

  1. Leloup v. Port of MobileSupreme Court of the United States · 1888
  2. Telegraph Co. v. TexasSupreme Court of the United States · 1882
  3. Chaffee & Co. v. United StatesSupreme Court of the United States · 1874
  4. Western Union Telegraph Co. v. TaylorSupreme Court of Georgia · 1890
  5. Western Union Telegraph Co. v. PettyjohnSupreme Court of Virginia · 1891

1 more not listed; retrieve them via the Exa API.

3Cited by13 opinions

  1. Western Union Telegraph Co. v. PowellSupreme Court of Virginia · 1897
  2. Western Union Telegraph Co. v. ReynoldsSupreme Court of Virginia · 1902
  3. Western Union Telegraph Co. v. GoddinSupreme Court of Virginia · 1897
  4. Commonwealth v. AdcockSupreme Court of Virginia · 1851
  5. Commonwealth v. AdcockSupreme Court of Virginia · 1851

8 more not listed; retrieve them via the Exa API.

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

Powered by the Exa API