Mount Ida (disambiguation)
Mount Ida, in Greek mythology, can refer to either of two mountains considered sacred:
- Mount Ida (Crete)
- Mount Ida (Turkey) or Phrygian Ida
Mount Ida may also refer to:
Mountains
- Mount Ida (Antarctica)
- Mount Ida (British Columbia), Canada
- Mount Ida (Colorado), U.S.
- Mount Ida, Tasmania, Australia, first ascended by a party that included Evelyn Temple Emmett
- Mount Ida, Heathcote, Victoria
related names
- Ida Ridge, AKA Mount Ida, an eroded cinder cone in east-central British Columbia, Canada
Places
Australia
- Mount Ida, Western Australia, an abandoned town
New Zealand
- Mount Ida (New Zealand electorate), a community and electorate
United States
- Mount Ida, Arkansas
- Mount Ida (Davenport, Iowa), a neighborhood that borders the Prospect Park Historic District
- Mont Ida, Kansas
- Mount Ida, Wisconsin, a town
- Mount Ida (community), Wisconsin, an unincorporated community in the town
- Mount Ida Plantation, a former plantation in Talladega County, Alabama
- Mt Ida (Ellicott City, Maryland), a historic home
- Mount Ida (Scottsville, Virginia), a historic home
Other uses
- Mount Ida College, in Newton, Massachusetts
- Mount Ida Gold Mine, a gold mine in Western Australia
gollark: If you configured it wrong during setup of whatever this is somehow, then it won't match. PotatOS has the law enforcement access mechanism (PS#7D7499AB) which also currently doubles as "forgot password" handling, but not every OS does that.
gollark: How do you know your password is the right one?
gollark: I should assign unique IDs to the other sandbox escape bugs.
gollark: My "fix" is this:```lua--[["Fix" for bug PS#E9DCC81BSummary: `pcall(getfenv, -1)` seemingly returned the environment outside the sandbox.Based on some testing, this seems like some bizarre optimization-type feature gone wrong.It seems that something is simplifying `pcall(getfenv)` to just directly calling `getfenv` and ignoring the environment... as well as, *somehow*, `function() return getfenv() end` and such.The initial attempt at making this work did `return (fn(...))` instead of `return fn(...)` in an attempt to make it not do this, but of course that somehow broke horribly. I don't know what's going on at this point.This is probably a bit of a performance hit, and more problematically liable to go away if this is actually some bizarre interpreter feature and the fix gets optimized away.Unfortunately I don't have any better ideas. Also, I haven't tried this with xpcall, but it's probably possible, so I'm attempting to fix that too.]]local real_pcall = pcallfunction _G.pcall(fn, ...) return real_pcall(function(...) local ret = {fn(...)} return unpack(ret) end, ...)end local real_xpcall = xpcallfunction _G.xpcall(fn, handler) return real_xpcall(function() local ret = {fn()} return unpack(ret) end, handler)end```which appears to work at least?
gollark: Fixed, but I don't really know how or why.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.